The Toggle Item node () is a menu option that toggles some state as a menu item in a parent menu or as a button on a toolbar. A toggle item can be useful for switching between a tabbed and a tiled look for a form collection, for example. You can add a Toggle Item node under a Menu node or to a Toolbar object in a form. Enter the name of the toggle item object in the Name field.

In the Text field, enter the text to display on the toggle menu item. To add an icon to the toggle menu item, specify an image file to use from the Icon list, which includes all of the images in the Images library, or click the Add Image to Library and Use Here button () to locate an image to use on the file system. That image then becomes a part of the Images library and is selected as the icon for this menu item. If you do not want to use an icon, select None from the Icon list. Click the Export button () to export the image to the file system (for use in another application, for example).

For Toggle Item nodes directly under a Ribbon Section, you can select Large (the default) or Small from the Size list. This size controls the size of the button in the ribbon.

For Toggle Item nodes directly under a Ribbon Section, you can also add a tooltip, which is a descriptive text that displays when the user hovers the pointer over the ribbon button, in the Tooltip field.

You can define a shortcut for the item that you enter in the Keyboard shortcut field. To add a keyboard shortcut, make the Keyboard shortcut field active, and then type a keyboard shortcut on the keyboard.

In addition, the Settings window contains the following sections.

This section contains a tree with a filtered view of the trees in the Application Builder and Model Builder windows. The nodes either represent some sort of data or have children that do. For a toggle item, strings and Boolean variable declarations (representing on and off states for the toggle item) under Declarations are available as sources. When you select a node that represents data, the Use as Source toolbar button below the tree becomes enabled. You can click it or, alternatively, press Enter, double-click, or right-click the node and choose Use as Source to add it as the selected source. You can also click the Create New Declaration and Use It as Source button () or the Create New Form Declaration and Use It as Source button () in the Source section header to create a new global or local (in the form) variable declaration for the toggle item and use it as the source. A Create and Use Variable dialog box opens, so that you can select the data type of the source (if applicable) and its name. The name cannot be in conflict with any existing variable declaration. Click the Edit Node toolbar button () below the tree to move to the corresponding node.

After selecting a node as the source, the node appears as the selected source under Selected source.

Typically, you only see the available parameters under the Parameters node, variables under a Variables node, and the data nodes defined under the Declarations branch in the Application Builder part of the application tree (underneath the Events branch). You can extend the list of available data nodes by clicking the Switch to Model Builder and Activate Data Access button () in the Source for Data Change section header, which takes you automatically to the Model Builder. Then, select a node in the Model Builder branch with data you want to access. With this button active, the Settings window of the selected node displays a Select Data Source check box (a green square) next to the settings that you can include. Select the check box to include this data as an available source node for events.

Any restrictions on a data source are passed along to the user interface of the application. For example, a Load type list in a Boundary Load node for structural mechanics only allows three values. Any form object using this data as its source can only support a subset of these values.

For a Toggle Item object, you can also specify if the initial value should be selected (on) or cleared (off). From the initial value list, select Custom value (the default) or From data source. For Custom value, choose Selected or Cleared from the Initial state list.

This section contains a tree with a filtered view of the trees in the Application Builder and Model Builder windows. The nodes either support a command or have children that do. When you select a node that supports one or more commands, the corresponding command toolbar buttons become enabled in the toolbar below the tree. You can also right-click a node to get a list of available commands for that particular node. Once you click a command with a node selected (or press Enter to add a command with its default command such as Run, Plot, or Set Value), the command and node appear in the last row of the table in the Choose Commands to Run section of the Settings window. This table contains all of the nodes that run. You can delete and move commands using the toolbar below the table.

In the Model branch, all of the nodes that represent some sort of data value, such as a parameter under the Parameters node, support the Set Value command. Add a Set Value command to the table to enable the third column, Arguments. In this column, you type the value to set. For data that represents arrays, use curly braces and commas to enter the array elements. For example, enter {1,2,3} to set a three-element array with the values 1, 2, and 3. See The Array 1D String Node for more details about how to enter arrays and matrices. For nodes that represent a file import, such as a Filename node under an Interpolation function node, an Import File command is available. You can also add a Plot command for all View nodes, providing the name of a Graphics object as the argument.

The tree includes a number of branches from the application tree in addition to the Model branch:

When you click one of the commands underneath the tree, the command appears under Command in the list below. There is also a Symbol column and an Arguments column, where you can enter any applicable arguments that the command uses. A tooltip appears indicating what type of argument the command expects. For example, for the downloadtoclient command, the argument is a file and its path, such as embedded:///myfile.txt, and there is a separate dialog box that helps you define such an argument. See File Schemes and File Handling for more information.

Click the Convert to Method toolbar button () and choose Convert to Method or Convert to Form Method to convert the entire list of commands in the table to a global or form method that contains the equivalent code. After this operation, the list of commands only contains a single Run operation on the created method. When you select a method under Command, or there is exactly one method in the list, you can go to the editor window for that method by clicking the Go to Method button (). For information about the Edit Argument button (), see Editing Initial Values and Arguments in Declarations and Command Sequences. Use the Move Up (), Move Down (), and Delete () toolbar buttons to organize and remove commands from the list (and the local method, if deleted).