The script has maybe 20-30 similar image detection blocks. A lot of the blocks use the wait/find pattern as shown in my example. It takes about 5 minutes to run the script, and I have it running every 10 minutes for testing, although it may go for long periods where it isn't running due to an failur...

Heh, no, as I said, the script works up until the point it doesn't. More specifically, it is an application run in a Citrix client so I don't want to rely on exact matching since I think it uses RDP internally. Regardless of the difficulty in matching, those methods should never return -1 as that is...

I think the last bug was specific to CCOEFF matching. I'm using the fuzzy matching algorithm because the application I am working with is in a remote desktop window.

All of the images used in my script are small in size (ex. menu items, buttons, list items).

I really don't think it has anything to do with the image itself. This is just the first image detection code in the script so when the the image detection engine fails it fails. In fact, when it first fails it could be on different code (assumption), but after that it would fail on this code since ...

It looks like image detection is failing over time. It stops working and returns error codes every time. This is like the issue I reported with Windows 2003 except that would happen within the first few runs. This problem is happening over the course of a few days. The memory usage is 130 MB which i...

Ok, the example is bad, and it is most likely due to a problem with the program (numfound = -1) which I've reported in another post. I still think the idea is useful for debugging false positives.

http://www.mjtnet.com/forum/viewtopic.php?p=34938#34938

I assume you mean WSI_TIMEOUT. I do have the timeout being set. I'm not sure the connection, unless you think the problem is with my script. The script runs fine most of the time, and the problem was that it was finding a match when it shouldn't (not timing out too quickly) which I'm positive was be...

I am the one that reported that issue. I have 14.0.12e.

I've reported a few other related issues, but I think this one is different. I recently had another weird issue with image detection where the WaitScreenImage wasn't timing out as expected and then the FindImagePos was failing. I didn't think to check if NUM_FOUND was -1 which indicates a failure, b...

It would be nice to have more information about what image detection is finding. For instance, between WaitScreenImage and FindImagePos only the latter provides coordinates of the image, and you would have to do something with them such as moving the mouse there to see what the match is. A problem I...

I am now using the close window method to close the window and the program is no longer crashing. This indicates to me that the IEQuit has a definite problem since it consistently crashed the program usually withing 20 runs of my script. I am using Windows 7 with IE 10 (I think it was 10 when the cr...

When debugging a particular section it can be time consuming to run the entire script up to that breakpoint (ex. if it takes 5 minutes to get the application in the appropriate state). I don't see how those techniques resolve the issue of only wanting to run a section at the top (ex. variable initia...

The step through debugger stops on every line whether it is a blank line or a comment. This process is already slow enough without stopping on lines that don't result in execution. A bit more complicated, but it would also be nice to reset the position. If I am testing a block of code I may need to ...

It failed again after 15 runs. This time it shows the end for the IEQuit as the last line in the log file which again shows it happens on the IEQuit or soon after. 7/1/2013 19:26:31:423 - START: 76: // logout and close browser 7/1/2013 19:26:31:423 - END: 76: // logout and close browser 7/1/2013 19:...

It seems to be failing on the closing of the browser using the specialized method. I've done a couple other tests, and it has failed either on the IEQuit line or soon after it (in the one case above it failed on a Wait immediately following the IEQuit). I will try to close the window using an altern...