Actions (Obsolete)

Important!: These actions have been deprecated in favor to Actions

Actions define the flow of the application once they have been fired. How it is exactly triggered the action depends of the name assigned to the field. By default, if the name doesn't contain a keyword to one of the 3 action types, then it is assumed that the action is a layout ID and it is executed in the OnClick event, but if such ID is not found, the action is treated as initiated by a method or a Firable Action.

There's several structures you can use to control your actions execution:

• [Action Parameters](About-flow-control (Obsolete)#action-parameters)
• [Executing java code](About-flow-control (Obsolete)#executing-java-code)
• [Conditionals](About-flow-control (Obsolete)#conditionals)

Actions in DecleX are initiated by:

• [The User Interface](Action Types (Obsolete)#the-user-interface)
• [On Events](Action Types (Obsolete)#on-events)
• [Existing Methods](Action Types (Obsolete)#existing-methods)

There's a set of available actions in DecleX

• [Enhanced Activities](Available-Actions (Obsolete)#enhanced-activities)
• [Enhanced Fragments](Available-Actions (Obsolete)#enhanced-fragments)
• [Events](Available-Actions (Obsolete)#events)
• [Models](Available-Actions (Obsolete)#models)
• [Android Components](Available-Actions (Obsolete)#android-components)