Binscatter Properties

R2026b

Binscatter appearance and behavior

Binscatter properties control the appearance and behavior of binned scatter plots. By changing property values, you can modify aspects of the display. Use dot notation to refer to a particular object and property:

h = binscatter(randn(1,100),randn(1,100));
N = h.NumBins
h.NumBins = [3 3]

Bins

NumBins — Number of bins

scalar | two-element vector

Number of bins, specified as a scalar or two-element vector [Nx Ny].

• If NumBins is specified as a two-element vector [Nx Ny], then binscatter uses Nx bins in the x dimension and Ny bins in the y dimension.

• If NumBins is specified as a scalar, then Nx and Ny are both set to the scalar value.

binscatter uses Nx and Ny bins along the x and y dimensions in the initial plot, when the axes are not zoomed in. (The axes are not zoomed in when the XLimMode and YLimMode properties are both "auto".) When zooming, binscatter adjusts the number of bins to maintain a bin size such that the visible portion of the plot is approximately divided into Nx-by-Ny bins.

The maximum number of bins in each dimension is 250. The default number of bins is computed based on the data size and standard deviation and does not exceed 100.

Example: [10 20]

Data Types: single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64

NumBinsMode — Selection mode for number of bins

"auto" (default) | "manual"

Selection mode for number of bins, specified as either "auto" or "manual". With the default value of "auto", the number of bins is computed from the data according to Scott's rule, [3.5*std(X(:))*numel(X)^(-1/4), 3.5*std(Y(:))*numel(Y)^(-1/4)].

If you specify the number of bins, then the value of NumBinsMode is set to "manual".

ShowEmptyBins — Toggle to show empty bins

"off" (default) | on/off logical value

Toggle to show empty bins, specified as either "off" or "on", or as numeric or logical 1 (true) or 0 (false). A value of "on" is equivalent to true, and "off" is equivalent to false. Thus, you can use the value of this property as a logical value. The value is stored as an on/off logical value of type matlab.lang.OnOffSwitchState.

Specify "on" or true to color tiles in the plot that fall within the bin limits, but have no data points.

XBinEdges — Bin edges in x-dimension

Read-only: vector

This property is read-only.

Bin edges in x-dimension, returned as a vector.

Data Types: single | double | datetime | duration

YBinEdges — Bin edges in y dimension

Read-only: vector

This property is read-only.

Bin edges in y dimension, returned as a vector.

Data Types: single | double | datetime | duration

XLimits — Data limits in x-dimension

vector

Data limits in x-dimension, specified as a two-element vector [Xmin Xmax].

binscatter only displays data points that fall within the specified data limits inclusively, $$X_{\min }\le X\le X_{\max }$$.

Example: [0 10]

Data Types: single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | datetime | duration

XLimitsMode — Selection mode for data limits in x-dimension

"auto" (default) | "manual"

Selection mode for data limits in x-dimension, specified as "auto" or "manual". The default value is "auto", so that the bin limits automatically adjust to the data along the x-axis.

If you explicitly specify XLimits, then XLimitsMode is automatically set to "manual". In that case, specify XLimitsMode as "auto" to rescale the bin limits to the data.

YLimits — Data limits in y-dimension

vector

Data limits in y-dimension, specified as a two-element vector [Ymin Ymax].

binscatter only displays data points that fall within the specified data limits inclusively, $$Y_{\min }\le Y\le Y_{\max }$$.

Example: [0 10]

Data Types: single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | datetime | duration

YLimitsMode — Selection mode for data limits in y-dimension

"auto" (default) | "manual"

Selection mode for data limits in y-dimension, specified as "auto" or "manual". The default value is "auto", so that the bin limits automatically adjust to the data along the y-axis.

If you explicitly specify YLimits, then YLimitsMode is automatically set to "manual". In that case, specify YLimitsMode as "auto" to rescale the bin limits to the data.

Data

XData — x coordinates of data

vector

x coordinates of data, specified as a vector.

Data Types: single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | datetime | duration

XDataMode — Control how XData is set

"auto" | "manual"

Since R2026a

Control how the XData property is set, specified as one of these values:

• "auto" — The XData property updates automatically based on the SourceTable and XVariable properties. This is the case when you pass a table to the binscatter function.

• "manual" — The XData property is set directly and does not update automatically. This is the case when you pass coordinate values as vectors to the binscatter function.

YData — y coordinates of data

vector

y coordinates of data, specified as a vector.

Data Types: single | double | int8 | int16 | int32 | int64 | uint8 | uint16 | uint32 | uint64 | datetime | duration

YDataMode — Control how YData is set

"auto" | "manual"

Since R2026a

Control how the YData property is set, specified as one of these values:

• "auto" — The YData property updates automatically based on the SourceTable and YVariable properties. This is the case when you pass a table to the binscatter function.

• "manual" — The YData property is set directly and does not update automatically. This is the case when you pass coordinate values as vectors to the binscatter function.

Values — Bin values

Read-only: double matrix vector

This property is read-only.

Bin values, returned as a double matrix. The (i,j)th entry in Values specifies the bin count for the bin whose x edges are [XBinEdges(i), XBinEdges(i+1)] and whose y edges are [YBinEdges(j), YBinEdges(j+1)].

The bin inclusion scheme for the different numbered bins in Values, as well as their relative orientation to the x-axis and y-axis, is

For example, the (1,1) bin includes values that fall on the first edge in each dimension. The last bin in the bottom right includes values that fall on any of its edges.

Table Data

Since R2026a

SourceTable — Source table

table | timetable

Source table containing the data to plot, specified as a table or timetable.

XVariable — Table variable containing x-coordinates

string scalar | character vector | pattern | numeric scalar | logical vector | vartype subscript

Table variable containing the x-coordinates, specified using one of the indexing schemes from the following table. The table variable you specify can contain numeric, logical, datetime, or duration values. When you set this property, MATLAB^® updates the XData property.

Indexing Scheme	Examples
Variable name: A string scalar or character vector. A pattern object. The pattern object must refer to only one variable.	"A" or 'A' — A variable named A "Var"+digitsPattern(1) — The variable with the name "Var" followed by a single digit
Variable index: An index number that refers to the location of a variable in the table. A logical vector. Typically, this vector is the same length as the number of variables, but you can omit trailing 0 or false values.	3 — The third variable from the table [false false true] — The third variable
Variable type: A vartype subscript that selects a table variable of a specified type. The subscript must refer to only one variable.	vartype("double") — The variable containing double values

YVariable — Table variable containing y-coordinates

string scalar | character vector | pattern | numeric scalar | logical vector | vartype subscript

Table variable containing the y-coordinates, specified using one of the indexing schemes from the following table. The table variable you specify can contain numeric, logical, datetime, or duration values. When you set this property, MATLAB updates the YData property.

Indexing Scheme	Examples
Variable name: A string scalar or character vector. A pattern object. The pattern object must refer to only one variable.	"A" or 'A' — A variable named A "Var"+digitsPattern(1) — The variable with the name "Var" followed by a single digit
Variable index: An index number that refers to the location of a variable in the table. A logical vector. Typically, this vector is the same length as the number of variables, but you can omit trailing 0 or false values.	3 — The third variable from the table [false false true] — The third variable
Variable type: A vartype subscript that selects a table variable of a specified type. The subscript must refer to only one variable.	vartype("double") — The variable containing double values

Color and Transparency

FaceColor — Tile color

"flat" | color name or short name | RGB triplet | hexadecimal color code | "none"

Since R2026b

Tile color, specified as one of these values:

• "flat" — Tile colors vary according to the bin counts. By default, the colors come from the sky colormap (in the light theme) or the abyss colormap (in the dark theme). You can change the colormap by calling the colormap function after plotting.

• Color name (or short name) — Tiles have a uniform color. Specify "red" (or "r"), "green" (or "g"), "blue" (or "b"), "cyan" (or "c"), "magenta" (or "m"), "yellow" (or "y"), "black" (or "k"), or "white" (or "w").

• RGB triplet — Tiles have a uniform color. An RGB triplet is a three-element row vector whose elements specify the intensities of the red, green, and blue components of the color. The intensities must be in the range [0,1]; For example, [0.4 0.6 0.7].

• Hexadecimal color code — Tiles have a uniform color. A hexadecimal color code is a string scalar or character vector that starts with a hash symbol (#) followed by three or six hexadecimal digits, which can range from 0 to F. The values are not case sensitive. The color codes "#FF8800", "#ff8800", "#F80", and "#f80" are equivalent.

• "none" — Tiles have no color.

This table lists the default color palettes for plots in the light and dark themes. You can use the colors from these palettes to match other plots.

Palette	Palette Colors
"gem" — Light theme default Before R2025a: Most plots use these colors by default.
"glow" — Dark theme default

To get the RGB triplets and hexadecimal color codes for these palettes , use the orderedcolors and rgb2hex functions. For example, get the RGB triplets for the "gem" palette and convert them to hexadecimal color codes.

RGB = orderedcolors("gem");
H = rgb2hex(RGB);

Example: binscatter(x,y,FaceColor="g") creates a binned scatter plot with green tiles.

Example: binscatter(x,y,FaceColor="#8B6CE0") creates a binned scatter plot with purple tiles.

Example: binscatter(x,y,FaceColor="flat") creates a binned scatter plot with tile colors that vary according to the bin counts.

FaceColorMode — Control how FaceColor is set

"auto" (default) | "manual"

Since R2026b

Control how the FaceColor property is set, specified as one of these values:

• "auto" — MATLAB controls the value of the FaceColor property depending on the values of other properties:

  • If the FaceAlpha property of the Binscatter object is a number, MATLAB sets the FaceColor property to "flat" and uses a colormap for the tile colors. This behavior is the default when you plot one data set with the binscatter function. You can distinguish bin counts within the plot by the different tile colors.

  • If the FaceAlpha property of the Binscatter object is "flat", MATLAB uses the SeriesIndex property of the Binscatter object and the ColorOrder property of the Axes object to control the colors of the faces. All tiles have the same hue with different transparency levels. This behavior is the default when you plot multiple data sets, either by passing matrices of data or multiple table variables to the binscatter function. You can distinguish one data set from another by the overall hue of each plot, and you can distinguish the bin counts within a plot by the different tile transparency levels.

• "manual" — The value of the FaceColor property does not change regardless of the SeriesIndex, FaceAlpha, and ColorOrder property values.

If you change the value of the FaceColor property manually, MATLAB changes the value of the FaceColorMode property to "manual".

FaceAlpha — Transparency of tiles

"flat" (since R2026b) | scalar in the range [0, 1]

Transparency of the tiles, specified as "flat" or as a scalar in the range [0, 1].

• "flat" — Vary the tile transparency according to the bin counts, where more opaque bins have higher counts. You can adjust the mapping of bin counts to the transparency levels using the alpha and alphamap functions. Specifying the FaceAlpha value as "flat" can cause the FaceColor property to change to a uniform color for all the bins instead of using a colormap. This change happens when the FaceColorMode property of the Binscatter object has a value of "auto" (the default value).

• Scalar in the range [0, 1] — Use the same transparency for all the tiles. A value of 1 means fully opaque and 0 means completely transparent (invisible).

Example: binscatter(x,y,FaceAlpha=0.5) creates a binned scatter plot with semitransparent bins.

Example: binscatter(x,y,FaceAlpha="flat") creates a binned scatter plot with tile transparencies that vary according to the bin counts. (since R2026b)

SeriesIndex — Series index

positive integer | "none"

Since R2026b

Series index, specified as a positive integer or "none". This property affects the color of a plot as long as the FaceAlpha property of the Binscatter object is "flat" and the FaceColorMode property has the default value of "auto". Then you can use this property to change the tile color so that it matches the color of another objects in the axes.

By default, the SeriesIndex property of a Binscatter object is a number that corresponds to its order of creation, starting at 1. MATLAB uses the number to calculate indices for assigning colors when you create multiple plots. The indices refer to the rows of the arrays stored in the ColorOrder property of the axes. Any objects in the axes that have the same SeriesIndex number have the same color.

A SeriesIndex value of "none" corresponds to a neutral color that does not participate in the indexing scheme.

How Manual Color Assignment Overrides SeriesIndex Behavior

To manually control tile color, set the FaceColor property of the Binscatter object to a color value, such as a color name or an RGB triplet.

When you manually set the tile color of a Binscatter object, MATLAB sets the FaceColorMode property to "manual" and disables automatic color selection for that object. Your color persists regardless of the value of the SeriesIndex property.

To enable automatic selection again, set the SeriesIndex property to positive integer, and set the FaceColorMode property to "auto".

In some cases, MATLAB sets the SeriesIndex property to 0, which also disables automatic color selection.

Legend

DisplayName — Text used by legend

variable name of Data or "" (default) | character vector

Text used by the legend, specified as a character vector. The text appears next to an icon of the binscatter.

Example: "Text Description"

For multiline text, create the character vector using sprintf with the new line character \n.

Example: sprintf("line one\nline two")

Alternatively, you can specify the legend text using the legend function.

• If you specify the text as an input argument to the legend function, then the legend uses the specified text and sets the DisplayName property to the same value.

• If you do not specify the text as an input argument to the legend function, then the legend uses the text in the DisplayName property. The default value of DisplayName is one of these values.

  • For numeric inputs, DisplayName is a character vector representing the variable name of the input data used to construct the histogram. If the input data does not have a variable name, then DisplayName is empty, "".

  • For categorical array inputs, DisplayName is empty, "".

If the DisplayName property does not contain any text, then the legend generates a character vector. The character vector has the form "dataN", where N is the number assigned to the binscatter object based on its location in the list of legend entries.

If you edit interactively the character vector in an existing legend, then MATLAB updates the DisplayName property to the edited character vector.

Annotation — Include object in legend

Annotation object

Include the object in the legend, specified as an Annotation object. Set the underlying IconDisplayStyle property of the Annotation object to one of these values:

• "on" — Include the object in the legend (default).

• "off" — Do not include the object in the legend.

For example, to exclude the Binscatter object named obj from the legend, set the IconDisplayStyle property to "off".

obj.Annotation.LegendInformation.IconDisplayStyle = "off";

Alternatively, you can control the items in a legend using the legend function. Specify the first input argument as a vector of the graphics objects to include. If you do not specify an existing graphics object in the first input argument, then it does not appear in the legend. However, graphics objects added to the axes after the legend is created do appear in the legend. Consider creating the legend after creating all the plots to avoid extra items.

Interactivity

Visible — State of visibility

"on" (default) | on/off logical value

State of visibility, specified as "on" or "off", or as numeric or logical 1 (true) or 0 (false). A value of "on" is equivalent to true, and "off" is equivalent to false. Thus, you can use the value of this property as a logical value. The value is stored as an on/off logical value of type matlab.lang.OnOffSwitchState.

• "on" — Display the object.

• "off" — Hide the object without deleting it. You still can access the properties of an invisible object.

DataTipTemplate — Data tip content

DataTipTemplate object

Data tip content, specified as a DataTipTemplate object. You can control the content that appears in a data tip by modifying the properties of the underlying DataTipTemplate object. For a list of properties, see DataTipTemplate Properties.

For an example of modifying data tips, see Create Custom Data Tips.

Note

The DataTipTemplate object is not returned by findobj or findall, and it is not copied by copyobj.

ContextMenu — Context menu

empty GraphicsPlaceholder array (default) | ContextMenu object

Context menu, specified as a ContextMenu object. Use this property to display a context menu when you right-click the object. Create the context menu using the uicontextmenu function.

Note

If the PickableParts property is set to "none" or if the HitTest property is set to "off", then the context menu does not appear.

Selected — Selection state

"off" (default) | on/off logical value

Selection state, specified as "on" or "off", or as numeric or logical 1 (true) or 0 (false). A value of "on" is equivalent to true, and "off" is equivalent to false. Thus, you can use the value of this property as a logical value. The value is stored as an on/off logical value of type matlab.lang.OnOffSwitchState.

• "on" — Selected. If you click the object when in plot edit mode, then MATLAB sets its Selected property to "on". If the SelectionHighlight property also is set to "on", then MATLAB displays selection handles around the object.

• "off" — Not selected.

SelectionHighlight — Display of selection handles

"on" (default) | on/off logical value

Display of selection handles when selected, specified as "on" or "off", or as numeric or logical 1 (true) or 0 (false). A value of "on" is equivalent to true, and "off" is equivalent to false. Thus, you can use the value of this property as a logical value. The value is stored as an on/off logical value of type matlab.lang.OnOffSwitchState.

• "on" — Display selection handles when the Selected property is set to "on".

• "off" — Never display selection handles, even when the Selected property is set to "on".

Callbacks

ButtonDownFcn — Mouse-click callback

"" (default) | function handle | cell array | string scalar | character vector

Mouse-click callback, specified as one of these values:

• Function handle

• Cell array in which the first element is a function handle and subsequent elements are the arguments to pass to the callback function

• String scalar or character vector containing a valid MATLAB command or function, which is evaluated in the base workspace (not recommended)

The ButtonDownFcn callback executes when you click the Binscatter object.

For more information on how to use function handles to define callback functions, see Create Callbacks for Graphics Objects.

Note

If the PickableParts property is set to "none" or if the HitTest property is set to "off", then this callback does not execute.

CreateFcn — Creation function

"" (default) | function handle | cell array | string scalar | character vector

Object creation function, specified as one of these values:

• Function handle

• Cell array in which the first element is a function handle and subsequent elements are the arguments to pass to the callback function

• String scalar or character vector containing a valid MATLAB command or function, which is evaluated in the base workspace (not recommended)

For more information about specifying a callback as a function handle, cell array, string scalar, or character vector, see Create Callbacks for Graphics Objects.

This property specifies a callback function to execute when MATLAB creates the object. MATLAB initializes all property values before executing the CreateFcn callback. If you do not specify the CreateFcn property, then MATLAB executes a default creation function.

Setting the CreateFcn property on an existing component has no effect.

If you specify this property as a function handle or cell array, you can access the object that is being created using the first argument of the callback function. Otherwise, use the gcbo function to access the object.

DeleteFcn — Deletion function

"" (default) | function handle | cell array | string scalar | character vector

Object deletion function, specified as one of these values:

• Function handle

• Cell array in which the first element is a function handle and subsequent elements are the arguments to pass to the callback function

• String scalar or character vector containing a valid MATLAB command or function, which is evaluated in the base workspace (not recommended)

For more information about specifying a callback as a function handle, cell array, string scalar, or character vector, see Create Callbacks for Graphics Objects.

This property specifies a callback function to execute when MATLAB deletes the object. MATLAB executes the DeleteFcn callback before destroying the properties of the object. If you do not specify the DeleteFcn property, then MATLAB executes a default deletion function.

If you specify this property as a function handle or cell array, you can access the object that is being deleted using the first argument of the callback function. Otherwise, use the gcbo function to access the object.

Callback Execution Control

Interruptible — Callback interruption

"on" (default) | on/off logical value

Callback interruption, specified as "on" or "off", or as numeric or logical 1 (true) or 0 (false). A value of "on" is equivalent to true, and "off" is equivalent to false. Thus, you can use the value of this property as a logical value. The value is stored as an on/off logical value of type matlab.lang.OnOffSwitchState.

This property determines if a running callback can be interrupted. There are two callback states to consider:

• The running callback is the currently executing callback.

• The interrupting callback is a callback that tries to interrupt the running callback.

MATLAB determines callback interruption behavior whenever it executes a command that processes the callback queue. These commands include drawnow, figure, uifigure, getframe, waitfor, and pause.

If the running callback does not contain one of these commands, then no interruption occurs. MATLAB first finishes executing the running callback, and later executes the interrupting callback.

If the running callback does contain one of these commands, then the Interruptible property of the object that owns the running callback determines if the interruption occurs:

• If the value of Interruptible is set to "off", then no interruption occurs. Instead, the BusyAction property of the object that owns the interrupting callback determines if the interrupting callback is discarded or added to the callback queue.

• If the value of Interruptible is set to "on", then the interruption occurs. The next time MATLAB processes the callback queue, it stops the execution of the running callback and executes the interrupting callback. After the interrupting callback completes, MATLAB then resumes executing the running callback.

Note

Callback interruption and execution behave differently in these situations:

• If the interrupting callback is a DeleteFcn, CloseRequestFcn, or SizeChangedFcn callback, then the interruption occurs regardless of the Interruptible property value.

• If the running callback is currently executing the waitfor function, then the interruption occurs regardless of the Interruptible property value.

• If the interrupting callback is owned by a Timer object, then the callback executes according to schedule regardless of the Interruptible property value.

Note

When an interruption occurs, MATLAB does not save the state of properties or the display. For example, the object returned by the gca or gcf command might change when another callback executes.

BusyAction — Callback queuing

"queue" (default) | "cancel"

Callback queuing, specified as "queue" or "cancel". The BusyAction property determines how MATLAB handles the execution of interrupting callbacks. There are two callback states to consider:

• The running callback is the currently executing callback.

• The interrupting callback is a callback that tries to interrupt the running callback.

The BusyAction property determines callback queuing behavior only when both of these conditions are met:

• The running callback contains a command that processes the callback queue, such as drawnow, figure, uifigure, getframe, waitfor, or pause.

• The value of the Interruptible property of the object that owns the running callback is set to "off".

Under these conditions, the BusyAction property of the object that owns the interrupting callback determines how MATLAB handles the interrupting callback. Specify the BusyAction property as one of these values:

• "queue" — Put the interrupting callback in a queue to be processed after the running callback finishes execution.

• "cancel" — Do not execute the interrupting callback.

PickableParts — Ability to capture mouse clicks

"visible" (default) | "none"

Ability to capture mouse clicks, specified as one of these values:

• "visible" — Capture mouse clicks only when visible. The Visible property must be set to "on". The HitTest property determines if the Binscatter object responds to the click or if an ancestor does.

• "none" — Cannot capture mouse clicks. Clicking the Binscatter object passes the click to the object behind it in the current view of the figure window. The HitTest property of the Binscatter object has no effect.

HitTest — Response to captured mouse clicks

"on" (default) | on/off logical value

Response to captured mouse clicks, specified as "on" or "off", or as numeric or logical 1 (true) or 0 (false). A value of "on" is equivalent to true, and "off" is equivalent to false. Thus, you can use the value of this property as a logical value. The value is stored as an on/off logical value of type matlab.lang.OnOffSwitchState.

• "on" — Trigger the ButtonDownFcn callback of the Binscatter object. If you have defined the ContextMenu property, then invoke the context menu.

• "off" — Trigger the callbacks for the nearest ancestor of the Binscatter object that meets one of these conditions:

  • HitTest property is set to "on".

  • PickableParts property is set to a value that enables the ancestor to capture mouse clicks.

Note

The PickableParts property determines if the Binscatter object can capture mouse clicks. If it cannot, then the HitTest property has no effect.

BeingDeleted — Deletion status

Read-only: on/off logical value

This property is read-only.

Deletion status, returned as an on/off logical value of type matlab.lang.OnOffSwitchState.

MATLAB sets the BeingDeleted property to "on" when the DeleteFcn callback begins execution. The BeingDeleted property remains set to "on" until the component object no longer exists.

Check the value of the BeingDeleted property to verify that the object is not about to be deleted before querying or modifying it.

Parent/Child

Parent — Parent

Axes object

Parent, specified as an Axes object.

Children — Children

empty GraphicsPlaceholder array | DataTip object array

Children, returned as an empty GraphicsPlaceholder array or a DataTip object array. Use this property to view a list of data tips that are plotted on the chart.

You cannot add or remove children using the Children property. To add a child to this list, set the Parent property of the DataTip object to the chart object.

HandleVisibility — Visibility of object handle

"on" (default) | "off" | "callback"

Visibility of the object handle in the Children property of the parent, specified as one of these values:

• "on" — Object handle is always visible.

• "off" — Object handle is invisible at all times. This option is useful for preventing unintended changes by another function. Set HandleVisibility to "off" to temporarily hide the handle during the execution of that function.

• "callback" — Object handle is visible from within callbacks or functions invoked by callbacks, but not from within functions invoked from the command line. This option blocks access to the object at the command line, but permits callback functions to access it.

If the object is not listed in the Children property of the parent, then functions that obtain object handles by searching the object hierarchy or querying handle properties cannot return it. Examples of such functions include the get, findobj, gca, gcf, gco, newplot, cla, clf, and close functions.

Hidden object handles are still valid. Set the root ShowHiddenHandles property to "on" to list all object handles regardless of their HandleVisibility property setting.

Identifiers

Type — Type of graphics object

Read-only: 'binscatter'

This property is read-only.

Type of graphics object, returned as 'binscatter'. Use this property to find all objects of a given type within a plotting hierarchy, such as searching for the type using findobj.

Tag — Object identifier

"" (default) | string scalar | character vector

Object identifier, specified as a string scalar or character vector. You can specify a unique Tag value to serve as an identifier for an object. When you need access to the object elsewhere in your code, you can use the findobj function to search for the object based on the Tag value.

UserData — User data

[] (default) | array

User data, specified as any MATLAB array. For example, you can specify a scalar, vector, matrix, cell array, character array, table, or structure. Use this property to store arbitrary data on an object.

If you are working in App Designer, create public or private properties in the app to share data instead of using the UserData property. For more information, see Share Data Within a Single App Designer App.

Version History

Introduced in R2017b

R2026b: Control tile color and transparency when plotting multiple data sets

If you create multiple binned scatter plots, you can adjust the color and transparency of each plot by setting these properties:

• FaceColor — Control the colors of the tiles.

• FaceAlpha — Set a uniform transparency level for all the tiles or vary the transparency according to the bin counts.

• SeriesIndex — Assign a different color to a binned scatter plot using the color palette stored in the axes ColorOrder property.

• FaceColorMode — Control whether the tile colors update when you set the FaceAlpha and SeriesIndex properties.

R2026a: Specify table data

Specify the table data for a binned scatter plot by setting the SourceTable, XVariable, and YVariable properties.

R2020a: UIContextMenu property is not recommended

Starting in R2020a, using the UIContextMenu property to assign a context menu to a graphics object or UI component is not recommended. Use the ContextMenu property instead. The property values are the same.

There are no plans to remove support for the UIContextMenu property at this time. However, the UIContextMenu property no longer appears in the list returned by calling the get function on a graphics object or UI component.