Is there a way to detect a pixel colour change without knowing the colour? I am guessing one would have to sample the colour first at a particular location and then do a pixel colour compare afterwards, right?
Pixel colour comparing should be straight forward but how do we sample the colour value at a particular location? Any action to do that?
Ideally, MMM should detect pixel colour change automatically, without concerning what the exact colour is.
I get it. Some logic like: 5 | RUN ACTION | DEFINE STRING VARIABLE | %STRING%::PIXEL At Location [X:1095 Y:421] 6 | IF | PIXEL COLOR | Color [%STRING%]::At Location [X:1095 Y:421] | IS THE SAME | ACTION That would be cool. I'll look into it...not promising anything might not get it in to the next update. I'm way to close to releasing the next version without adding another feature lol it'll have to wait
Hurrah!! Steve u r on the ball! Exactly what I was looking for! I can think of so many applications for this!
Better yet, if u can build it all into the code as a function, the 1 liner may look something like this:
6 | IF | PIXEL COLOR | At Location [X:1095 Y:421] | Has changed | 1 time | Continue/Action -just detecting a single colour change at X,Y location and then action. Otherwise wait.
6 | IF | PIXEL COLOR | At Location [X:1095 Y:421] | Has changed | 2 times | Continue/Action -don't action until the colour has changed 2 times! Otherwise wait.
6 | IF | PIXEL COLOR | At Location [X:1095 Y:421] | Has changed | 3 times | Continue/Action
-don't action until the colour has changed 3 times! Otherwise wait.
This is so convenient as you don't have to worry about the exact colour that the webpage will give u. BTW, the last sampled colour can be stored in the internal variable %COLOR%! This should be useful for future use perhaps lol!
Look forward to the future release containing this new feature Steve!
Wow wow wow! Steve! You are absolutely brilliant and you have done it again! Such a welcome surprise and thank you so much! It was a super fast development cycle despite the coding challenge! I was also thinking about the time delay between the changes and wasn't sure how to handle it properly! Coz there might be some fast flashes on the screen (like a full screen pop-down menu etc) that you want to ignore. Looks like the CHANGES::X::X::X instruction is taking care of that! Congratulations once again Steve! An excellent feature addition to boost the power, reliability and simplicity of MMM immensely for web automation and any other applications that need to wait for a certain screen response! This is so awesome Steve and you deserve all the credit! I just ate the delicious spaghetti lol! Can't wait for the next release!!