Condition ‐ Screen ‐ Condition List

Interface

Screen Conditions are one of the two component of a Screen Event. They determine what should be displayed on your screen in order to execute the Actions associated to your Event.

The Screen Condition menu can be accessed from the Screen Event dialog, by clicking on the Condition section. Here it is empty, but once you will create your Conditions, they will be displayed here.

This will leads you to the Screen Condition list screen, allowing you to create, modify and reorder your Screen Conditions.

	The Screen Condition menu shows the state of your Screen Event Condition list. Here it is empty, but once your Condition created, they will appear here. More actions are available on the floating menu.
	Creates a new Screen Condition for your Screen Event
	Creates a new Screen Condition from an existing one for your Screen Event. You need to have created at least Screen Condition for this option to be available.
	Shows/hide the overlay. Usefull to interact with your phone while the app is started.
	Save your changes and return to the Screen Event Menu.

Once you have created some Screen Conditions, more action will be available at the bottom of the screen:

	The details of you currently displayed Screen Condition can be seen at the bottom of the screen. You can swipe left/right on the card to display the previous/next Screen Condition in the list.
	Swap this Screen Condition with the item on its left, increasing its priority
	Swap this Screen Condition with the item on its right, decreasing its priority
	Change the priority and index of this Screen Condition to a defined value. Usefull to avoid spamming move left/right buttons.
	Test your Screen Condition in live. Usefull to verify your configuration without having to execute your whole scenario.
	Delete the Screen Condition

Priority

As you can see, you can control the order/priority of the Screen Conditions in you list. Why does it matter ? Because Klick'r engine will execute the screen detection with the same order as your list.

Controlling the priority of your Screen Conditions can be useful in two cases:

• When using a Click Action that clicks on the detected Screen Condition in a Screen Event that uses the condition operator OR: when using this operator, the detection will stops at the first Screen Condition fulfilled and the Click Action will be executed on it.
• When trying to optimize your scenario timings. If you have two Screen Conditions to check in the same Screen Event, and one of them is smaller than the other, you can set the small Screen Condition before the big one, as if the small one is not fulfilled (or fulfilled for OR operator), Klick'r will not check the big one as it will not change the outcome of this Screen Event conditions verification.