Same brand monitor, same resolution, same color depth, and most importantly the same color profiles (no profile).

The script above can be easily run if you have a solid color desktop background and horizontally placed monitors.

Thanks

I have had many false positives when trying to transport compiled scripts from either Email, Discord, other messaging, or Uploads. My quick solution was to encrypt the Zip file so the transport mechanism cannot scan it and flag it. Then give the password to the end-user. The end user PC will still d...

Bumping

X2 should always be larger than X1
Y2 should always be larger than Y1

The coordinate are always Top Left, Bottom Right.

The previous scripts show Y2 is smaller than Y1

Here is a test script, the desktop background was changed to Solid Red so the CRC should be equal. This was compiled and tested on Win7 and Win10, MS 15.0.19b with the same results. Other functions like GetPixel, WaitPixelColor, ScreenCapture all work fine when working with the secondary monitor //S...

I'll do more testing on this end.

For the results above I was using Win7, MS 15.0.19, and Y1=Y2, a horizontal line essentially. I'll try Y1 and Y2=Y1+1 instead. If that fails I'll try Win10.

Thanks for the tips.

Using GetRectCheckSum on extended monitors returns unexpected results and always seems to return the same value no mater the bounding rectangle within the second monitor. As expected, use of GetRectCheckSum on the primary monitor works as intended.

Blindly installed version 19b, now waiting for release notes

fingers crossed for deleting and re-diming dynamic variables

Thanks for the workaround, if this behavior is intended then I'll continue using this workaround.

Hi again, as the title suggests i am Unable to set TIME OnEvent during a Button OnClick event, the code immediately exits the SRT after the OnEvent and the OnEvent is never set and fired at the selected time. The below code is arbitrary code for example only. Thank you. If this behavior is intended ...

Could I get confirmation that these quirks are intended and I can continue to find workarounds on my own. Thank you.

Same, creates {"THISARRAY_%WW%"} array Just so this thread does not get lost in it main purpose I will re-list the quirks: ArrayDim>THISARRAY_%WW%,8,integer ArrayDim>THISARRAY_%WW%,11,integer Re-dim'ing a multi-dim array creates an unexpected array DelArray>THISARRAY_%WW% Cannot delete a multi-dim a...

Just did it made these vars

One more quirk, BUT i found a workaround to Let>WW=2 Let>QINDX=55,66,77,88,99,11 Separate>QINDX,COMMA,THISARRAY_%WW%,integer This creates an array THISARRAY_%WW% instead of THISARRAY_2 , but the workaround below works Let>WW=2 Let>QINDX=55,66,77,88,99,11 Separate>QINDX,COMMA,TMPARRAY,integer ArrayCo...

Hi again :D some time back I came across these quirks and hopefully can get a workaround or solution. The first is reDim'ing multidimensional arrays, the following code creates 2 separate arrays THISARRAY_2 and THISARRAY_%WW% , of course the second array is unexpected. Let>WW=2 //make array with 8 e...