RPMIndicator Properties

Control revolutions per minute (RPM) indicator appearance and behavior

RPM indicators are components that represent an RPM indicator. Properties control the appearance and behavior of an RMP indicator. Use dot notation to refer to a particular object and property:

f = uifigure;
rpm = uiaerorpm(f);
rpm.Value = 100;

The RPM indicator displays measurements for engine revolutions per minute in percentage of RPM.

The range of values for RPM goes from 0 to 110%. Minor ticks represent increments of 5% RPM and major ticks represent increments of 10% RPM.

RMP Indicator

expand all

Minimum and maximum indicator scale values, specified as a two-element numeric array. The first value in the array must be less than the second value. This value is read-only.

If you change Limits such that the Value property is less than the new lower limit, or more than the new upper limit, then the indicator needle points to a location off the scale.

For example, suppose Limits is [0 100] and the Value property is 20. If the Limits changes to [50 100], then the needle points to a location off the scale, slightly less than 50.

Location of the RPM indicator needle, specified a finite and scalar numeric rev/min.

  • Changing the value changes the location of the to align with the corresponding value on the indicator.

Example: 60

Dependencies

Specifying this value changes the value of Value.

Data Types: double

Scale colors, specified one of the following arrays:

  • An n-by-3 array of RGB triplets

  • A cell array containing RGB triplets, any of the color options listed in the table below, or a combination of both.

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]. Alternatively, you can specify some common colors by name. This table lists the long and short color name options and the equivalent RGB triplet values.

OptionDescriptionEquivalent RGB Triplet
'red' or 'r'Red[1 0 0]
'green' or 'g'Green[0 1 0]
'blue' or 'b'Blue[0 0 1]
'yellow' or 'y'Yellow[1 1 0]
'magenta' or 'm'Magenta[1 0 1]
'cyan' or 'c'Cyan[0 1 1]
'white' or 'w'White[1 1 1]
'black' or 'k'Black[0 0 0]

Each color of the ScaleColors array corresponds to a colored section of the gauge. Set the ScaleColorLimits property to map the colors to specific sections of the gauge.

If you do not set the ScaleColorLimits property, MATLAB® distributes the colors equally over the range of the gauge.

Scale color limits, specified as an n-by-2 array of numeric values. For every row in the array, the first element must be less than the second element.

When applying colors to the gauge, MATLAB applies the colors starting with the first color in the ScaleColors array. Therefore, if two rows in ScaleColorLimits array overlap, then the color applied later takes precedence.

The gauge does not display any portion of the ScaleColorLimits that falls outside of the Limits property.

If the ScaleColors and ScaleColorLimits property values are different sizes, then the gauge shows only the colors that have matching limits. For example, if the ScaleColors array has three colors, but the ScaleColorLimits has only two rows, then the gauge displays the first two color/limit pairs only.

Location of the RPM indicator needle, specified a finite and scalar numeric rev/min.

  • Changing the value changes the location of the to align with the corresponding value on the indicator.

Example: 60

Dependencies

Specifying this value changes the value of RPM.

Data Types: double

Interactivity

expand all

Visibility of the RPM indicator, specified as 'on' or 'off'. The Visible property determines whether the RPM indicator is displayed on the screen. If the Visible property is set to 'off', then the entire RPM indicator is hidden, but you can still specify and access its properties.

Operational state of RPM indicator, specified as 'on' or 'off'.

  • If you set this property to 'on', then the appearance of the RPM indicator indicates that the RPM indicator is operational.

  • If you set this property to 'off', then the appearance of the RPM indicator appears dimmed, indicating that the RPM indicator is not operational.

Position

expand all

Location and size of the RPM indicator relative to the parent container, specified as the vector, [left bottom width height]. This table describes each element in the vector.

ElementDescription
leftDistance from the inner left edge of the parent container to the outer left edge of an imaginary box surrounding the RPM indicator
bottomDistance from the inner bottom edge of the parent container to the outer bottom edge of an imaginary box surrounding the RPM indicator
widthDistance between the right and left outer edges of the RPM indicator
heightDistance between the top and bottom outer edges of the RPM indicator

All measurements are in pixel units.

The Position values are relative to the drawable area of the parent container. The drawable area is the area inside the borders of the container and does not include the area occupied by decorations such as a menu bar or title.

Example: [200 120 120 120]

Inner location and size of the RPM indicator, specified as [left bottom width height]. Position values are relative to the parent container. All measurements are in pixel units. This property value is identical to the Position property.

This property is read-only.

Outer location and size of the RPM indicator returned as [left bottom width height]. Position values are relative to the parent container. All measurements are in pixel units. This property value is identical to the Position property.

Layout options, specified as a GridLayoutOptions object. This property specifies options for components that are children of grid layout containers. If the component is not a child of a grid layout container (for example, it is a child of a figure or panel), then this property is empty and has no effect. However, if the component is a child of a grid layout container, you can place the component in the desired row and column of the grid by setting the Row and Column properties on the GridLayoutOptions object.

For example, this code places an RPM indicator in the third row and second column of its parent grid.

g = uigridlayout([4 3]);
gauge = uiaerorpm(g);
gauge.Layout.Row = 3;
gauge.Layout.Column = 2;

To make the RPM indicator span multiple rows or columns, specify the Row or Column property as a two-element vector. For example, this RPM indicator spans columns 2 through 3:

gauge.Layout.Column = [2 3];

Callbacks

expand all

Object creation function, specified as one of these values:

  • Function handle.

  • Cell array in which the first element is a function handle. Subsequent elements in the cell array are the arguments to pass to the callback function.

  • Character vector containing a valid MATLAB expression (not recommended). MATLAB evaluates this expression in the base workspace.

For more information about specifying a callback as a function handle, cell array, or character vector, see Write Callbacks in App Designer (MATLAB).

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.

Object deletion function, specified as one of these values:

  • Function handle.

  • Cell array in which the first element is a function handle. Subsequent elements in the cell array are the arguments to pass to the callback function.

  • Character vector containing a valid MATLAB expression (not recommended). MATLAB evaluates this expression in the base workspace.

For more information about specifying a callback as a function handle, cell array, or character vector, see Write Callbacks in App Designer (MATLAB).

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

expand all

Callback interruption, specified as 'on' or 'off'. The Interruptible 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.

Whenever MATLAB invokes a callback, that callback attempts to interrupt the running callback (if one exists). The Interruptible property of the object owning the running callback determines if interruption is allowed. The Interruptible property has two possible values:

  • 'on' — Allows other callbacks to interrupt the object's callbacks. The interruption occurs at the next point where MATLAB processes the queue, such as when there is a drawnow, figure, uifigure, getframe, waitfor, or pause command.

    • If the running callback contains one of those commands, then MATLAB stops the execution of the callback at that point and executes the interrupting callback. MATLAB resumes executing the running callback when the interrupting callback completes.

    • If the running callback does not contain one of those commands, then MATLAB finishes executing the callback without interruption.

  • 'off' — Blocks all interruption attempts. The BusyAction property of the object owning the interrupting callback determines if the interrupting callback is discarded or put into a queue.

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.

  • Timer objects execute according to schedule regardless of the Interruptible property value.

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.

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.

Whenever MATLAB invokes a callback, that callback attempts to interrupt a running callback. The Interruptible property of the object owning the running callback determines if interruption is permitted. If interruption is not permitted, then the BusyAction property of the object owning the interrupting callback determines if it is discarded or put in the queue. These are possible values of the BusyAction property:

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

  • 'cancel' — Does not execute the interrupting callback.

This property is read-only.

Deletion status, returned as 'off' or 'on'. 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

expand all

Visibility of the object handle, specified as 'on', 'callback', or 'off'.

This property controls the visibility of the object in its parent's list of children. When an object is not visible in its parent's list of children, it is not returned by functions that obtain objects by searching the object hierarchy or querying properties. These functions include get, findobj, clf, and close. Objects are valid even if they are not visible. If you can access an object, you can set and get its properties, and pass it to any function that operates on objects.

HandleVisibility ValueDescription
'on'The object is always visible.
'callback'The object 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 allows callback functions to access it.
'off'The object is invisible at all times. This option is useful for preventing unintended changes to the UI by another function. Set the HandleVisibility to 'off' to temporarily hide the object during the execution of that function.

Parent container, specified as a Figure object created using the uifigure function, or one of its child containers: Tab, Panel, ButtonGroup, or GridLayout. If no container is specified, MATLAB calls the uifigure function to create a new Figure object that serves as the parent container.

Identifiers

expand all

This property is read-only.

Type of graphics object, returned as 'uiaerorpm'.

Object identifier, specified as a character vector or string scalar. 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.

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 App Designer Apps (MATLAB).

Introduced in R2018b