1

Enhancement: Flash (Tasker Layout) Interaction Variable

Right now the Flash Notices with "Tasker Layout" are pretty powerful; I use them basically everywhere as a cheap way to get user notices/interactions and have some aesthetic flexibility.

One enhancement I'd like to suggest is to add a special variable that gets passed to the "Perform Task" option for how it was dismissed, alongside adding swipe up/down/left/right and click/long-click detection.

*Note: Might need a bool checkbox to "enable gesture swipes" since some users may not want swiping enabled for some notices.

The various gestures would all act like the current "dismiss", except they'd pass a "dismiss method" variable.

  • If the Perform Task is set, the variable passes into that.
  • If the "continue task immediately" is not set, the variable is passed inline (same Task can use it downstream of the notice).
  • If the notice times out it could receive "timeout" as the dismiss method.
  • If the notice is replaced it could receive "replaced" as the dismiss method.

Any Perform Task assigned already receives the local vars of the notice spawning Task at time of creation, so those and the dismiss method would give great flexibility to doing further (simple) user interactions based on the dismiss type.

Example:

  1. Flash Notice is configured with Tasker Layout and to have the Perform Task as a custom router to act upon the passed in dismiss method. Flash is configured to "enable gesture swipes".
  2. Notice is spawned by the Task.
  3. User Swipes Up on the notice and the called Task detects the dismiss method as swipe_up, calling another Perform Task (assigned from logic in the PT "custom router" Task that was assigned as part of the notice).
  4. Another go around, the user dismisses with a long_click and the custom router Task calls a different PT.