Skip to main content

ProGlove documentation

Screen actions

Screen actions define what should happen when an interaction with an element associated with a screen occurs. Actions can be assigned to:

  • Screen components (e.g., buttons, list items) – Defines what should happen when a screen component is clicked

  • Action button (physical buttons associated with the screen) – Defines what should happen when a physical button is pressed

  • Screen Timer (automatically triggers after the defined delay) – Defines what should happen when a Screen Timer expires

Supported screen actions

  • Navigate back – Closes the current screen and returns to the previous one (if any). Useful for creating manual back navigation in workflows.

  • Notify – Triggers a callback to the integrator as an event. This is typically used when the application should handle the event itself — for example, to perform navigation, call a backend, or update local state.

    The triggered event includes screen context, which should be used to identify the screen where the interaction occurred. Depending on where the action is set, different types of events are triggered:

    • Screen component – Triggers a screen event (display_v2-event in Streams API) of type ScreenComponentClicked, including the reference ID of the clicked component and the screen context.

    • Screen Timer – Triggers a screen event (display_v2-event in Streams API) of type ScreenTimerExpired, including the screen context.

    • Action button – Triggers a button event that includes screen context and the physical button index. Each physical button has a fixed and predefined index that does not change with orientation or hand preference settings. However, the visual position of the action buttons on the screen can vary depending on hand preference. To determine which action button was clicked, use the screen context along with the physical button index.

      The SDK also provides a helper method: ButtonPress.getCorrespondingPgActionButtonReferenceId(), which returns the reference ID of the action button assigned to the pressed physical button at the time of the event.

  • Click on screen component – This action simulates a user click on another screen component and is primarily used to trigger interactions indirectly. It is commonly assigned to elements like Screen Timers or action buttons to activate components that support click behavior — including those with implicit behavior, such as text fields with assigned input method.

    A typical use case is initiating input by simulating a click on a text field that has an input method assigned. While the text field itself doesn’t support explicit actions, this mechanism allows external triggers (like timers or buttons) to start the input process by clicking the field. The targeted component must exist on the same screen and support click behavior, either implicit (e.g., text field with input method) or explicit (e.g., button, list item).

  • None – No action will be triggered. This is used to explicitly specify that no behavior should occur and any interaction should be ignored. For example, assigning None to a list item disables clicks on it, reducing unnecessary noise in the integration.

In this section: