Your method for finding the number (if it is only 3 digits) seems like it will work and is not actually so complicated. I'd suggest you try it and see how accurate it proves to be. As for combining the numbers simply use Concat> at the beginning of your code use Let>TheNumber= then as you find the a...

Remember SetControlText> ? I have used this in the past to force the name of any current windows to be the names I need for my immediate task (testing being one of them). Takes a little digging in View System Windows, and you'd still have to have some window with which to work...maybe use a few fold...

All good suggestions so far, but let me also state the you need to be sure the fonts are the same, the font smoothing setting, etc...Also, if you could use FindImgPos, then you could check the setting for number of pixels to check. Something like let>FIP_SCANPIXELS=1000 or whatever number you feel w...

If you would like to click on any "state" of an image but would rather not have to manage the code, the images, folders, etc...

Just ask for a download of AppNavigator. It will do the same thing.

Here is a simple filter you can use within Macro Script. let>validchar=0123456789 let>Str2Chk=123%456 let>Pos2Chk=0 len>Str2Chk,LenOfStr let>CleanStr= label>StartCheck let>Pos2Chk=Pos2Chk+1 if>Pos2Chk>LenOfStr goto>EndCheck endif midstr>Str2Chk,Pos2Chk,1,Char2Chk pos>Char2Chk,validchar,1,Found if>Fo...

Bob, If you remember to put values in " " which are strings and no " " when the variable or literal is numeric, it will work perfectly evertime. If you are comparing a variable which might be either, then include the " ". So you first example of : If>{(%ThisRecord%=##EOF##) AND (%FileLine%=2)} shoul...

You should test the GetText commands in Macro Scheduler. The "100%" accuracy will depend on many things, but you should be able to write some redundancy into your code which will make the "reading" of the data quite dependable. Of course, once you have the data captured correctly, you could have our...

Phil,

It is not uncommon that a compiled script runs slightly faster than the uncompiled version, so the fact that it only crashes when compiled is not surprising and the suggestion to add very small wait> times makes sense.

Have you tried the wait>.05 suggested and, if so, what are the results?

If you want your code to go to a specific label when it is NOT checked, then just tell it to do so. IF>SomeStatement=True goto>DoTrueLabel else goto>DoFalseLabel endif Your code is not easy to follow and it is not clear what you are trying to do. Also, if you want to do something while incrementing ...

You should also look into the use of IGNORESPACES. This setting will allow you to use spaces in some instances with no change in the value. This is right out of the help file By default, spaces are seen as regular characters and are included in variable assignments. E.g. The following line.. Let>a =...

so, then you are not passing any variable to your subroutine, but it is written to expect a variable.

put % signs around the variable so that a value shows in the log file. and be sure you call the subroutine with a variable.

Go to the macro properties and turn on logging. Then run the macro, let it hang and then look at the log file.

I notice you are sending the window name to a subroutine as a variable. Unless that is the EXACT window name, you might want to add an * at the end of the variable name so that it will find any window name beginning with the variable value. Also, be sure to set a WW_TIMEOUT to some value that is rea...

Go to the Tools menu, then select Options, then uncheck "Show Running indicator when hidden"

Why not download the eval of v10 (current version) and test again?

I think we would all be very interested in the result.