You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if the keep executing option is working. What I did was very simple.
I created event_1 and asked the software to detect image_1 which is on screen_1. Once image_1 is detected, i asked it to click on a specific place and wait for 2 seconds. Then click on another specific place and wait for 2 seconds and so on.
Everytime it clicked as per instructions in (1.) image_2 will show on screen_2.
Then, I created an event_2 to detect image_2 on screen_2, and i asked it to click on a specific position on screen_2 when image_2 is detected.
Event_2 will do the desired click and screen_1 will show again.
So ideally flow should be like,
Event_1 does its first click, waits 2 seconds,
Image_2 on screen_2 pops up while event_1 is waiting.
Event_2 will see image_2 on screen_2 and it will click.
This will show screen_1 again.
2 seconds wait will be over and the event_1 will continue it's execution from where it left (click 2).
then event_2 will again do it's click.
But in reality event_2 never executes and event_1 keeps clicking.
What I am saying is, this programme stops detection for other image events when one event is running it's instructions.
And even if it keeps checking and detecting for other image events while one event is running, it surely doesn't execute any instructions from another event as long as event 1 is running it's own instructions.
Describe the usage
This will allow component use and stop long list of actions for repatative use. Like, auto accepting confirmation dialogs, when clicking on a screen.
Is it a duplicate?
There is no duplicates
The text was updated successfully, but these errors were encountered:
Describe the feature
I am not sure if the keep executing option is working. What I did was very simple.
I created event_1 and asked the software to detect image_1 which is on screen_1. Once image_1 is detected, i asked it to click on a specific place and wait for 2 seconds. Then click on another specific place and wait for 2 seconds and so on.
Everytime it clicked as per instructions in (1.) image_2 will show on screen_2.
Then, I created an event_2 to detect image_2 on screen_2, and i asked it to click on a specific position on screen_2 when image_2 is detected.
Event_2 will do the desired click and screen_1 will show again.
So ideally flow should be like,
Event_1 does its first click, waits 2 seconds,
Image_2 on screen_2 pops up while event_1 is waiting.
Event_2 will see image_2 on screen_2 and it will click.
This will show screen_1 again.
2 seconds wait will be over and the event_1 will continue it's execution from where it left (click 2).
then event_2 will again do it's click.
But in reality event_2 never executes and event_1 keeps clicking.
What I am saying is, this programme stops detection for other image events when one event is running it's instructions.
And even if it keeps checking and detecting for other image events while one event is running, it surely doesn't execute any instructions from another event as long as event 1 is running it's own instructions.
Describe the usage
This will allow component use and stop long list of actions for repatative use. Like, auto accepting confirmation dialogs, when clicking on a screen.
Is it a duplicate?
The text was updated successfully, but these errors were encountered: