Anyone with experience using the Screen Content trigger and the Read Screen action in the same macro?
Have you noticed that performing a Read Screen action will cause a Screen Content trigger to fire if you're reading the same screen you have a trigger set up for? This is very annoying. Am I missing something ?
I am using a screen content trigger to activate some processing on the contents of that screen when it appears. My first action after the trigger runs the macro is to read the screen so I have access to all the information on it. Is this necessary or does the screen trigger process also store the screen contents somewhere I can access it so a subsequent read of the screen isn't necessary? If not, triggering a second start of the macro is not desirable and it's a pain to work around that.
I am familiar with how Tasker approaches this and it passes all the screen contents in an array to the triggered task. Very handy.
Have you noticed that performing a Read Screen action will cause a Screen Content trigger to fire if you're reading the same screen you have a trigger set up for? This is very annoying. Am I missing something ?
I am using a screen content trigger to activate some processing on the contents of that screen when it appears. My first action after the trigger runs the macro is to read the screen so I have access to all the information on it. Is this necessary or does the screen trigger process also store the screen contents somewhere I can access it so a subsequent read of the screen isn't necessary? If not, triggering a second start of the macro is not desirable and it's a pain to work around that.
I am familiar with how Tasker approaches this and it passes all the screen contents in an array to the triggered task. Very handy.
