Workaround for Separate shortcommings:
ArrayCopy expectedly copies THISARRAY to PRIZECNT_3_n

Thank you for pushing that to them. I now also discovered this does not work either, whether by design or not: Let>WW=6 Separate>0;0;0;0;0;0,;,PRIZECNT_%WW%,integer I thought i read a blog post or forum post talking about using %..% within commands, it was a feature added at one version, and I thoug...

Does someone have the link to the blog that talks about multidim arrays? i can't ever find those blogs, thanks.

The below script does not crash when ArrayFind finds a value, but does crash when it does NOT find a value. ArrayDim>PRIZECNT,6 Separate>0;0;0;0;0;0,;,PRIZECNT_1,integer Separate>0;0;0;0;7;0,;,PRIZECNT_2,integer Separate>0;0;0;0;0;0,;,PRIZECNT_3,integer Separate>0;0;0;0;0;0,;,PRIZECNT_4,integer Sepa...

Ok great thank you. I had a feeling that sometimes it did work but never thought to check it in the If-Else area instead. Happy gobble gobble!

thank you, in the mean time i am going to install the trial on a VM to see if i can indeed recreate the problem.

As a courtesy i also ran the above code as-is, it worked as normal and jumped to the correct location as expected. on Registered MS15.0.14. No word yet on my If> problems, I had to visit 'another' site to get a hint of my problem

Could we get an update to the limitations of complex expressions in If> statements please, thank you.

Testing every condition of every complex expression is taking a long time. We should have trust in the interpreter that it works as stated.

it is a happy sight to see owners solve their own problems as in this case. Great job solving the problem. Although, id be negligent in not offering a tip, instead of using notepad (*.txt) why not use internal MS15 arrays to store the data. this way you dont need to find a spot for the "C:\Users\use...

PS, I am citing https://www.mjtnet.com/manuals/v15/HTML ... sions.html as my basis for the above problems in it where it says complex function, including string functions, are "are supported in Macro Scheduler's IF statements and LET statement"

PROBLEM SOLVED! Here is the brute force code that will prevent the problem from happening above, DO NOT use complex expressions in If>{..} statements, rather just use the normal code provided by MS15. This code is functionally identical to the original code, no complex expression/functions are used ...

OHHHHHH SNAP!! So, the MS15 interpreter is ignoring any If>{pos/copy} when looking for exit points, in the example code the exact matching number of Endif's are provided by the ignored If>{pos/copy} staements which is why the exit point is where it is (wrong place). So current solution is not to use...

All my compiled macros that are to be portable include code to "train" image on the target computer, meaning on first run the macro will record (screencapture) the needed needles. it is not much of a problem if the resolution is different but once the DPI changes as it does on laptops 110dpi to desk...

Has anyone verified the problem? Or is the owners manual incorrect in saying that complex expressions can be used with If statements? Thank you.

Just wondering how deep this rabbit hole goes or if im doing something wrong.

I just noticed when I use the Copy function or the Pos function within a complex If>{...} statement that it causes unexpected but predictable exit location of earlier If statements, please see this code, keep in mind all the code is arbitrary to recreate the problem. Thank you for looking. I am now ...