06-11-2015, 02:04 PM
Thank you - your support is fast and helpful.
I cannot currently recreate this error as it has only happened once out of hundreds of executions of the macro but I am worried it may happen again on rare occasions.
I think that the scan probably returned a "window not found" error as the macro runs extremely fast and the screen was changing from displaying an old window to activating a new window (as you mentioned when destroying there may be no active window for a brief moment)
I think that in QM 2.4.3.0 scan with the flag x1000 "scan" will check for a color in a window both for active or even if it is not active ? So windows both not visible or visible on the screen may be scanned for colors without activating them?
So if I use the window number (handle) rather than "win" with "scan" then I should never get this error again as I do not need to activate the window to scan for the colour?
e.g. use
int w1=123456
scan("color:0x0" w1 r2 0x1000)
and NOT
scan("color:0x0" win r2 0x1000)
I cannot currently recreate this error as it has only happened once out of hundreds of executions of the macro but I am worried it may happen again on rare occasions.
I think that the scan probably returned a "window not found" error as the macro runs extremely fast and the screen was changing from displaying an old window to activating a new window (as you mentioned when destroying there may be no active window for a brief moment)
I think that in QM 2.4.3.0 scan with the flag x1000 "scan" will check for a color in a window both for active or even if it is not active ? So windows both not visible or visible on the screen may be scanned for colors without activating them?
So if I use the window number (handle) rather than "win" with "scan" then I should never get this error again as I do not need to activate the window to scan for the colour?
e.g. use
int w1=123456
scan("color:0x0" w1 r2 0x1000)
and NOT
scan("color:0x0" win r2 0x1000)