Altova MobileTogether Designer

This command is enabled for those controls that can be associated with a page source node and for which an association exists. Unassign Page Source <Name> deletes the association between control and page source. Note that there is no other way to delete the control's association with a node.

Displays the Control Actions dialog, in which you can set actions for various control events. For a description of available actions for control events and how to set control actions, go to the section, Page Design | Actions.

Opens the control's Local Variables dialog, where you can add, edit, and delete the variables of the control. A control variable has a name, which is a string, and a value, which is an XPath expression. The variables that are declared in the Local Variables dialog will be evaluated when the control is called and will be used with the corresponding values till the control is called again. Parameters can be used in the XPath expression that calculates a variable's value.

Control variables are useful for providing values that can be used in control actions. Consider, for example, a Department node inside a Company node where the domain name of each Company node (for example, altova.com or nanonull.com) is provided in a child node of the Company node. If you now set a control variable to select the domain-name node, then the control variable can be used in an action of the control to dynamically select each company's domain name when that company is being processed. For example, the email addresses of a department's Employee children can be built by using each employee's FirstName and LastName elements together with the control variable that contains the company's domain name.

Control variables can also be set via a control's Control Variables property (available in the Styles & Properties pane when the control is selected). The currently defined control variables are listed as sub-items of the Control Variables property; each control variable can be edited by double-clicking it.

Enabled for controls in which text can be entered. Rolls out a sub-menu with the following options:

•Directly: To enter static text directly as the text of the control

•XPath: Displays the Edit XPath/XQuery Expression dialog, in which you can enter the XPath expression that selects the text of the control

•XML Node: Refers to the option of displaying the content of an XML node as the control's text. Clicking the option displays a hint that a page source node can be dragged from the Page Sources Pane onto the control. The dragged-and-dropped node will be associated with the control, and the node's content will be entered as the text of the control

Displays the Localization dialog, in which you can define the localization (translation) of strings that appear in various controls of the project. This command has the same effect as the Project | Localization command. For a description of localization, go to the description of the Project | Localization command.

If a control has a file that can be deployed or if an Image control has a file that can be embedded, then the respective sub-commands of the Deploy/Embed File command are enabled.

•For the option to deploy a file, you can choose the sub-command for where you want to deploy the file. On deployment, the file is added to the Deployable Files list of the Files Pane.

•When you embed an image file, the binary data of the image file (PNG, BMP, etc) is converted into text-based Base64-encoding, and this text is embedded in the design file. On embedding, the Image control's Embed Image property is set to true. See the description of the property for more information.

If a control template can be created from the selected design component/s, then the Create Template from Selection command is enabled. Selecting the command does the following: (i) adds to the project a new control template that contains the selected design component/s (see the Pages Pane); (ii) replaces the selected design component/s with a Placeholder Control. To return to the previous state, use the context menu command Replace Placeholder with Template Content (see description immediately below).

This command is enabled when for Placeholder Controls, which are controls that instantiate a control template of the project. The command replaces the Placeholder Control with the content of the control template for which it is a placeholder. Note that neither the control template nor its content is deleted. The reverse command is Create Template from Selection (see description immediately above).

Displays the Device Dependent Visibility dialog (screenshot below). The dialog contains a list of client-device types. Select the client-device type for which you want the control to be visible, and click OK.

If the client-device type has an icon, this icon appears in the design, to the left of the control to which it applies (see screenshot below).

Displays the Page Actions dialog, in which you can set actions for various page events. This command has the same effect as the Page | Page Actions command. For a description of available actions for page events and how to set page actions, go to the description of the Page | Page Actions command.

Displays the Actions Overview dialog of the currently active page. This command has the same effect as the Page | Actions Overview command. For more information, go to the description of the Page | Actions Overview command.