A scene is a graphical user-interface consisting of a collection of elements to which tasks can be attached to be run when the user interacts with them e.g. by tapping them.
Tasker uses scenes for things like popup dialogs, menus and getting input from the user but scenes can actually be displayed by the user whenever desired, meaning they can be used for things like creating simple user-designed applications or showing extra controls over the top of (selected) existing applications.
Scenes are completely user-customisable via a drag-and-drop graphical editor.
Enter Key, HTML Popup, Lock, Menu, Popup, Popup Task Buttonsand
Popupactions have the same style because they all use the same scene.
The parameters specified in the action are applied to the scene before it is show. For instance, if the scene has a Title element it will be set to the title specified in the action and the scene resized appropriately.
It might be desirable to have a different style for e.g. some
Popup actions, in which case:
Popupaction, specify that the cloned scene should be used by clicking on the Layout parameter in the action edit screen.
Create Scene, Show Scene, Hide Scene, Destroy Scene
Show Scene and
Destroy Scene will be
used, however sometimes it's useful for a scene to be created but not visible to
An element has three main components:
Specified under the UI tab in the element editor. Some elements also have a Background tab. A Menu element has an additional Items tab.
Specified under the right-most tabs after clicking on the element in the element editor. There are different events depending on the type of element. For instance, a Button has tap and long-tap events while a Slider has a value-set event.
Event tasks are run at priority one higher than the task which displayed the scene
Local variables set by event tasks are visible to all tasks in the same scene.
Note that actions that affect scene elements can only be used when the scene has
already been created (via
Create Scene or
The scene does not have to be visible.