Thank you for your question. First, let me assure you it's not a trial limitation. It also isn't any kind of a bug that I'm aware we've come across or had reported before. I just tried to replicate this used the Wizard 28 times in a row to successfully create code and images, before I stopped testin...

Glad you found it.

Kind regards,

Dorian.

Thank you for your suggestion. A possible workaround for this could be :

Let>IGNOREERRORS=1
FindObject>blah blah
Let>IGNOREERRORS=0

Thank you! We'll take a look at that.

Hi Peter,

Please feel free to send an email to [email protected] and we'd be more than happy to guide you through creating the script you need.

If I'm understanding correctly, this may be a workaround. So you're running a script which encounters an external problem, and cannot complete it's tasks until you fix the external problem. You then want it to run again once the problems are fixed. How about this : 1. Make the script write to an out...

It sounds like your macros12.dat might have become corrupted. I suggest : Exit Macro Scheduler Locate macros12.dat in your data folder, which by default would be My Documents\Macro Scheduler 14. Rename macro12.dat to macros12.old Rename one of the macros12 backup files to macro12.dat. These will be ...

Having researched this I can see only one instance of it being reported before, and that was when the user was attempting to compile an exe to DropBox. Could it be that?

Recently, I've been using Macro Scheduler to.... back up all my macros. It simply zips up my entire \Macro Scheduler 14 folder and subfolders, and saves the zipfile to my OneDrive. Using the Macro Scheduler Timer and CountFiles functions, I can report that I just backed up 809 files in 2.581 seconds...

This is a little puzzling, as CCOEFF wasn't in v11 so I can't imagine tweaking that tolerance will make any difference at all. It was introduced in v14. There have been some major Image Recognition improvements since v11. Version 14.0.2 31/01/2013 - Script Additions/Improvements: - New portable/tole...

A tolerance of 1 is looking for an exact match. If you mean to make it 100% pixel to pixel precise then use EXACT.

Try lowering the tolerance. If it wasn't matching at 0.7, try 0.6, and so on.

mightycpa wrote:No, you don't have to compile, just run it from this view:

Yes, MightCPA is correct. Thank you for clarifying.

I think the first question to ask is whether you're using Correlation Coefficient, or Exact Match?

I would try Correlation Coefficient and then experiment with the Tolerance setting.

I've attached a screenshot of the Image Recognition Wizard in case it helps.

If we didn't have moments like that, we wouldn't be human. That's why I have snippets like that to make up for my (very occasional) shortcomings.

That sounds like it would streamline things wonderfully. I'm downloading that now so I can have a play with it. I've found command line tools combined with Macro Scheduler to be a very powerful combination in the past.