Struct plotly::traces::Scatter3D

pub struct Scatter3D<X, Y, Z>where
    X: Serialize + Clone,
    Y: Serialize + Clone,
    Z: Serialize + Clone,{ /* private fields */ }

Construct a scatter3D trace.

Examples

use plotly::Scatter3D;

let trace = Scatter3D::new(
    vec![0.0, 1.0],
    vec![2.0, 3.0],
    vec![4.0, 5.0],
);

let expected = serde_json::json!({
    "type": "scatter3d",
    "x": [0.0, 1.0],
    "y": [2.0, 3.0],
    "z": [4.0, 5.0],

});

assert_eq!(serde_json::to_value(trace).unwrap(), expected);

Implementations

impl<X, Y, Z> Scatter3D<X, Y, Z>where X: Serialize + Clone, Y: Serialize + Clone, Z: Serialize + Clone,

pub fn name(self, value: impl AsRef<str>) -> Box<Self>

Sets the trace name. The trace name is used as the label for the trace in the legend, as well as when the trace is hovered hover.

pub fn modify_all_name(value: impl AsRef<str>) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_name(values: Vec<impl AsRef<str>>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn visible(self, value: Visible) -> Box<Self>

Determines whether or not this trace is visible. If Visible::LegendOnly, the trace is not drawn, but can appear as a legend item (provided that the legend itself is visible).

pub fn modify_all_visible(value: Visible) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_visible(values: Vec<Visible>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn show_legend(self, value: bool) -> Box<Self>

Determines whether or not an item corresponding to this trace is shown in the legend.

pub fn modify_all_show_legend(value: bool) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_show_legend(values: Vec<bool>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn legend_group(self, value: impl AsRef<str>) -> Box<Self>

Sets the legend group for this trace. Traces part of the same legend group show/hide at the same time when toggling legend items.

pub fn modify_all_legend_group( value: impl AsRef<str> ) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_legend_group( values: Vec<impl AsRef<str>> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn legend_rank(self, value: usize) -> Box<Self>

Sets the legend rank for this trace. Items and groups with smaller ranks are presented on top/left side while with "reversed" legend.traceorder` they are on bottom/right side. The default legendrank is 1000, so that you can use ranks less than 1000 to place certain items before all unranked items, and ranks greater than 1000 to go after all unranked items.

pub fn modify_all_legend_rank(value: usize) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_legend_rank(values: Vec<usize>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn legend_group_title(self, value: LegendGroupTitle) -> Box<Self>

Sets the LegendGroupTitle object for the trace.

pub fn modify_all_legend_group_title( value: LegendGroupTitle ) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_legend_group_title( values: Vec<LegendGroupTitle> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn opacity(self, value: f64) -> Box<Self>

Sets the opacity of the trace.

pub fn modify_all_opacity(value: f64) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_opacity(values: Vec<f64>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn mode(self, value: Mode) -> Box<Self>

Determines the drawing mode for this scatter trace. If the provided Mode includes “Text” then the text elements appear at the coordinates. Otherwise, the text elements appear on hover. If there are less than 20 points and the trace is not stacked then the default is Mode::LinesMarkers, otherwise it is Mode::Lines.

pub fn modify_all_mode(value: Mode) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_mode(values: Vec<Mode>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn ids(self, value: Vec<impl AsRef<str>>) -> Box<Self>

Assigns id labels to each datum. These ids for object constancy of data points during animation. Should be an array of strings, not numbers or any other type.

pub fn modify_all_ids(value: Vec<impl AsRef<str>>) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_ids( values: Vec<Vec<impl AsRef<str>>> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn x(self, value: Vec<X>) -> Box<Self>

pub fn modify_all_x(value: Vec<X>) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_x(values: Vec<Vec<X>>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn y(self, value: Vec<Y>) -> Box<Self>

pub fn modify_all_y(value: Vec<Y>) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_y(values: Vec<Vec<Y>>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn z(self, value: Vec<Z>) -> Box<Self>

pub fn modify_all_z(value: Vec<Z>) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_z(values: Vec<Vec<Z>>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn surface_color(self, value: impl Color) -> Box<Self>

Sets the surface fill color.

pub fn modify_all_surface_color(value: impl Color) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_surface_color( values: Vec<impl Color> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn text(self, value: impl AsRef<str>) -> Box<Self>

Sets text element associated with each (x, y, z) triplet. The same tet will be applied to each data point. If the trace HoverInfo contains a “text” flag and hover_text is not set, these elements will be seen in the hover labels.

pub fn modify_all_text(value: impl AsRef<str>) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_text(values: Vec<impl AsRef<str>>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn text_array(self, value: Vec<impl AsRef<str>>) -> Box<Self>

Sets text element associated with each (x, y, z) triplet. The same tet will be applied to each data point. If the trace HoverInfo contains a “text” flag and hover_text is not set, these elements will be seen in the hover labels.

pub fn text_position(self, value: Position) -> Box<Self>

Sets the positions of the text elements with respects to the (x, y) coordinates.

pub fn modify_all_text_position(value: Position) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_text_position(values: Vec<Position>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn text_position_array(self, value: Vec<Position>) -> Box<Self>

Sets the positions of the text elements with respects to the (x, y) coordinates.

pub fn text_template(self, value: impl AsRef<str>) -> Box<Self>

Template string used for rendering the information text that appear on points. Note that this will override textinfo. Variables are inserted using %{variable}, for example “y: %{y}”. Numbers are formatted using d3-format’s syntax %{variable:d3-format}, for example “Price: %{y:$.2f}”. See format for details on the formatting syntax. Dates are formatted using d3-time-format’s syntax %{variable|d3-time-format}, for example “Day: %{2019-01-01|%A}”. See format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are arrayOk: true) are available.

pub fn modify_all_text_template( value: impl AsRef<str> ) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_text_template( values: Vec<impl AsRef<str>> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn text_template_array(self, value: Vec<impl AsRef<str>>) -> Box<Self>

Template string used for rendering the information text that appear on points. Note that this will override textinfo. Variables are inserted using %{variable}, for example “y: %{y}”. Numbers are formatted using d3-format’s syntax %{variable:d3-format}, for example “Price: %{y:$.2f}”. See format for details on the formatting syntax. Dates are formatted using d3-time-format’s syntax %{variable|d3-time-format}, for example “Day: %{2019-01-01|%A}”. See format for details on the date formatting syntax. Every attributes that can be specified per-point (the ones that are arrayOk: true) are available.

pub fn hover_text(self, value: impl AsRef<str>) -> Box<Self>

Sets hover text elements associated with each (x, y, z) triplet. The same text will be associated with all datas points. To be seen, the trace hover_info must contain a “Text” flag.

pub fn modify_all_hover_text( value: impl AsRef<str> ) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_hover_text( values: Vec<impl AsRef<str>> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn hover_text_array(self, value: Vec<impl AsRef<str>>) -> Box<Self>

Sets hover text elements associated with each (x, y, z) triplet. The same text will be associated with all datas points. To be seen, the trace hover_info must contain a “Text” flag.

pub fn hover_info(self, value: HoverInfo) -> Box<Self>

Determines which trace information appears on hover. If HoverInfo::None or HoverInfo::Skip are set, no information is displayed upon hovering. But, if HoverInfo::None is set, click and hover events are still fired.

pub fn modify_all_hover_info(value: HoverInfo) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_hover_info(values: Vec<HoverInfo>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn hover_template(self, value: impl AsRef<str>) -> Box<Self>

Template string used for rendering the information that appear on hover box. Note that this will override HoverInfo. Variables are inserted using %{variable}, for example “y: %{y}”. Numbers are formatted using d3-format’s syntax %{variable:d3-format}, for example “Price: %{y:$.2f}”. https://github.com/d3/d3-3.x-api-reference/blob/master/Formatting.md#d3_format for details on the formatting syntax. Dates are formatted using d3-time-format’s syntax %{variable|d3-time-format}, for example “Day: %{2019-01-01|%A}”. https://github.com/d3/d3-3.x-api-reference/blob/master/Time-Formatting.md#format for details on the date formatting syntax. The variables available in hovertemplate are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are arrayOk: true) are available. Anything contained in tag <extra> is displayed in the secondary box, for example “{fullData.name}”. To hide the secondary box completely, use an empty tag <extra></extra>.

pub fn modify_all_hover_template( value: impl AsRef<str> ) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_hover_template( values: Vec<impl AsRef<str>> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn hover_template_array(self, value: Vec<impl AsRef<str>>) -> Box<Self>

Template string used for rendering the information that appear on hover box. Note that this will override HoverInfo. Variables are inserted using %{variable}, for example “y: %{y}”. Numbers are formatted using d3-format’s syntax %{variable:d3-format}, for example “Price: %{y:$.2f}”. https://github.com/d3/d3-3.x-api-reference/blob/master/Formatting.md#d3_format for details on the formatting syntax. Dates are formatted using d3-time-format’s syntax %{variable|d3-time-format}, for example “Day: %{2019-01-01|%A}”. https://github.com/d3/d3-3.x-api-reference/blob/master/Time-Formatting.md#format for details on the date formatting syntax. The variables available in hovertemplate are the ones emitted as event data described at this link https://plotly.com/javascript/plotlyjs-events/#event-data. Additionally, every attributes that can be specified per-point (the ones that are arrayOk: true) are available. Anything contained in tag <extra> is displayed in the secondary box, for example “{fullData.name}”. To hide the secondary box completely, use an empty tag <extra></extra>.

pub fn x_hover_format(self, value: impl AsRef<str>) -> Box<Self>

Sets the hover text formatting rulefor x using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3’s date formatter: “%h” for half of the year as a decimal number as well as “%{n}f” for fractional seconds with n digits. For example, “2016-10-13 09:15:23.456” with tickformat “%H~%M~%S.%2f” would display “09~15~23.46”. By default the values are formatted using x_axis.hover_format.

pub fn modify_all_x_hover_format( value: impl AsRef<str> ) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_x_hover_format( values: Vec<impl AsRef<str>> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn y_hover_format(self, value: impl AsRef<str>) -> Box<Self>

Sets the hover text formatting rulefor y using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3’s date formatter: “%h” for half of the year as a decimal number as well as “%{n}f” for fractional seconds with n digits. For example, “2016-10-13 09:15:23.456” with tickformat “%H~%M~%S.%2f” would display “09~15~23.46”. By default the values are formatted using y_axis.hover_format.

pub fn modify_all_y_hover_format( value: impl AsRef<str> ) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_y_hover_format( values: Vec<impl AsRef<str>> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn z_hover_format(self, value: impl AsRef<str>) -> Box<Self>

Sets the hover text formatting rulefor z using d3 formatting mini-languages which are very similar to those in Python. For numbers, see: https://github.com/d3/d3-format/tree/v1.4.5#d3-format. And for dates see: https://github.com/d3/d3-time-format/tree/v2.2.3#locale_format. We add two items to d3’s date formatter: “%h” for half of the year as a decimal number as well as “%{n}f” for fractional seconds with n digits. For example, “2016-10-13 09:15:23.456” with tickformat “%H~%M~%S.%2f” would display “09~15~23.46”. By default the values are formatted using z_axis.hover_format.

pub fn modify_all_z_hover_format( value: impl AsRef<str> ) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_z_hover_format( values: Vec<impl AsRef<str>> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn meta(self, value: impl Into<NumOrString>) -> Box<Self>

Assigns extra meta information associated with this trace that can be used in various text attributes. Attributes such as trace name, graph, axis and colorbar title.text, annotation text rangeselector, updatemenues and sliders label text all support meta. To access the trace meta values in an attribute in the same trace, simply use %{meta[i]} where i is the index or key of the meta item in question. To access trace meta in layout attributes, use %{data[n[.meta[i]} where i is the index or key of the meta and n is the trace index.

pub fn modify_all_meta( value: impl Into<NumOrString> ) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_meta( values: Vec<impl Into<NumOrString>> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn custom_data( self, value: Vec<impl Into<NumOrString> + Clone> ) -> Box<Self>

Assigns extra data each datum. This may be useful when listening to hover, click and selection events. Note that, “scatter” traces also appends customdata items in the markers DOM elements.

pub fn modify_all_custom_data( value: Vec<impl Into<NumOrString> + Clone> ) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_custom_data( values: Vec<Vec<impl Into<NumOrString> + Clone>> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn scene(self, value: impl AsRef<str>) -> Box<Self>

Sets a reference between this trace’s 3D coordinate system and a 3D scene. If “scene” (the default value), the (x,y,z) coordinates refer to layout.scene. If “scene2”, the (x, y, z) coordinates refer to layout.scene2, and so on.

pub fn modify_all_scene(value: impl AsRef<str>) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_scene(values: Vec<impl AsRef<str>>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn marker(self, value: Marker) -> Box<Self>

Determines how points are displayed and joined.

pub fn modify_all_marker(value: Marker) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_marker(values: Vec<Marker>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn line(self, value: Line) -> Box<Self>

Line display properties.

pub fn modify_all_line(value: Line) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_line(values: Vec<Line>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn error_x(self, value: ErrorData) -> Box<Self>

x-axis error display properties.

pub fn modify_all_error_x(value: ErrorData) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_error_x(values: Vec<ErrorData>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn error_y(self, value: ErrorData) -> Box<Self>

y-axis error display properties.

pub fn modify_all_error_y(value: ErrorData) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_error_y(values: Vec<ErrorData>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn error_z(self, value: ErrorData) -> Box<Self>

z-axis error display properties.

pub fn modify_all_error_z(value: ErrorData) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_error_z(values: Vec<ErrorData>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn connect_gaps(self, value: bool) -> Box<Self>

Determines whether or not gaps (i.e. {nan} or missing values) in the provided data arrays are connected.

pub fn modify_all_connect_gaps(value: bool) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_connect_gaps(values: Vec<bool>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn hover_label(self, value: Label) -> Box<Self>

Properties of label displayed on mouse hover.

pub fn modify_all_hover_label(value: Label) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_hover_label(values: Vec<Label>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn projection(self, value: Projection) -> Box<Self>

Configure the projection for each axis.

pub fn modify_all_projection(value: Projection) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_projection(values: Vec<Projection>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn surface_axis(self, value: SurfaceAxis) -> Box<Self>

If SurfaceAxis::MinusOne, the scatter points are not filled with a surface. If one of the remaining three variants, the scatter points are filled with a Delaunay surface about the x, y, z respectively.

pub fn modify_all_surface_axis(value: SurfaceAxis) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_surface_axis( values: Vec<SurfaceAxis> ) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn x_calendar(self, value: Calendar) -> Box<Self>

Sets the calendar system to use with x date data.

pub fn modify_all_x_calendar(value: Calendar) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_x_calendar(values: Vec<Calendar>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn y_calendar(self, value: Calendar) -> Box<Self>

Sets the calendar system to use with y date data.

pub fn modify_all_y_calendar(value: Calendar) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_y_calendar(values: Vec<Calendar>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

pub fn z_calendar(self, value: Calendar) -> Box<Self>

Sets the calendar system to use with z date data.

pub fn modify_all_z_calendar(value: Calendar) -> RestyleScatter3D<X, Y, Z>

Apply the same restyling to all the traces

pub fn modify_z_calendar(values: Vec<Calendar>) -> RestyleScatter3D<X, Y, Z>

Apply the restyling individually to each trace. Caller is responsible to set the length of the vector to be equal to the number of traces

impl<X, Y, Z> Scatter3D<X, Y, Z>where X: Serialize + Default + Clone, Y: Serialize + Default + Clone, Z: Serialize + Default + Clone,

pub fn new(x: Vec<X>, y: Vec<Y>, z: Vec<Z>) -> Box<Self>

Trait Implementations

impl<X, Y, Z> Clone for Scatter3D<X, Y, Z>where X: Serialize + Clone + Clone, Y: Serialize + Clone + Clone, Z: Serialize + Clone + Clone,

fn clone(&self) -> Scatter3D<X, Y, Z>

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl<X, Y, Z> Debug for Scatter3D<X, Y, Z>where X: Serialize + Clone + Debug, Y: Serialize + Clone + Debug, Z: Serialize + Clone + Debug,

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<X, Y, Z> Default for Scatter3D<X, Y, Z>where X: Serialize + Clone, Y: Serialize + Clone, Z: Serialize + Clone,

fn default() -> Self

Returns the “default value” for a type.

impl<X, Y, Z> Serialize for Scatter3D<X, Y, Z>where X: Serialize + Clone + Serialize, Y: Serialize + Clone + Serialize, Z: Serialize + Clone + Serialize,

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>where __S: Serializer,

Serialize this value into the given Serde serializer.

impl<X, Y, Z> Trace for Scatter3D<X, Y, Z>where X: Serialize + Clone, Y: Serialize + Clone, Z: Serialize + Clone,

fn to_json(&self) -> String