-
Hello! I need some help in understanding how the “Not Visible” option for a condition is supposed to work. My naive understanding is that the condition should evaluate to true if the image in the condition cannot be found. However, I am not able to get this to work in an ‘and’ condition context. In the ‘or’ context it works as expected. Here’s a description of my problem, how I have approached it, what the result of my approach is, and what my desired behaviour would be. I want to join a queue. There are 5 spaces in the queue and a certain symbol indicates that the spot in the queue is open. I really want to join the queue, but I do not want to be first. I have three image conditions that I have captured. One is the item I want to queue for. One is the open first position in the queue, and one is the join queue button which is visible when it is possible to join the queue. In my screen event I have for the conditions: AND:
I have found that the ‘not visible’ part of the condition seems to be ignored when running the scenario. In the ‘or’ context, it will activate the event as long as the ‘not visible’ condition has disappeared from the screen. However, in the ‘and’ context the conditions will evaluate to true as a whole even if the first queue position is visible. When running ‘test screen event’ it shows a red square over the position were the condition is evaluated when the position is filled, and green when it is open. This gives me the opposite behaviour from what I want. I will join when the queue is empty, but I will not join when the first position has been filled. Am I trying to use the condition incorrectly? If so, how can I create an event that is triggered in the way I want it to? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I have experimented some more, and found that the feature does work as I imagined it would, and that my event is just badly tuned! |
Beta Was this translation helpful? Give feedback.
I have experimented some more, and found that the feature does work as I imagined it would, and that my event is just badly tuned!