You can use FireMonkey actions to provide response from various UI elements in your FireMonkey applications.
What Is an Action
An action corresponds to one or more elements of the user interface, such as menu commands, toolbar buttons, and controls.
Actions serve two functions:
- Actions represent properties common to the user interface elements, such as whether a control is enabled or a check box, selected.
- Actions respond when a control fires, for example, when the application user clicks a button or chooses a menu item.
An action is associated with a client and acts on a target:
- Clients--one or more clients use the action. When the client receives a user command (such as a mouse click), it initiates an associated action.
- Targets--the action acts on the target. A target is usually a control, such as a memo or a data control. Not all actions use a target.
FireMonkey Actions in XE3
Beginning from version XE3, FireMonkey supports actions and action lists:
- Framework-independent action features are implemented in the RTL in the System.Classes.TBasicAction and System.Classes.TBasicActionLink classes of the System.Classes unit and in classes of the System.Actions unit.
- FireMonkey framework-specific action features are implemented in the FMX units FMX.ActnList, FMX.StdActns, and others. For more details, see Actions in FireMonkey.
- FireMonkey supports FMX action lists. You can group FMX actions in FMX action lists using the Action List editor. FMX actions inserted into FMX action lists can be assigned to client components--UI elements of your application (menu commands, toolbar buttons, and other controls). These actions respond when a control fires.
- Actions in FireMonkey