5 days left on my evaluation period, and the sample macro Text Capture suddenly stopped working; it displays the dialog box, but does not return any text from any spot on screen, and will not capture text for any open window -- it just moves focus to the selected window, but returns no text.
And my test macro that uses GetTextAtPoint>x,y,mouseText,nChar returns nothing in the variable mouseText, even though x,y are valid coordinates.
Before today, both the sample macro and my own test macro worked fine.
Any ideas? Running on WinXP Pro SP2.
Screen captures no longer working
Moderators: JRL, Dorian (MJT support)
Try restarting Macro Scheduler to see if the problem goes away. If so, then this may be the same problem that I have reported with various text capture commands. The problem occurs when you invoke a second copy of Macro Scheduler via a bat file or cmd prompt. For some reason that second copy of Macro Scheduler (no matter what it does) causes the text capture commands to stop working on the first, original copy of Macro Scheduler.
Screen captures
Thanks for the info. I did not have a second copy of MSched running, but after a re-boot, the screen capture is working again, and so far has not yet recurred.
Still wondering what may have caused the loss of functionality. I'm concerned about putting compiled scripts out there for 15-20 users who each may encounter this problem.
Still wondering what may have caused the loss of functionality. I'm concerned about putting compiled scripts out there for 15-20 users who each may encounter this problem.
There are various ways that a second copy of Macro Scheduler is automatically started and then that copy ends as soon as the called macro ends. One way is the "Create Desktop Shortcut" option. If you use that option, and then start the desktop shortcut, then any macros that are later started from the main Macro Scheduler menu that have text capture commands , like the Text Capture sample script, will fail.
Screen captures
Does this same problem present itself when executing compiled scripts solely from desktop shortcuts? My plan is to compile executables, place them on a shared drive, and have my users execute them via desktop shortcuts. They will execute multiple times per day, multiple scripts.
Is this implementation plan going to hit a snag because of this glitch?
Is this implementation plan going to hit a snag because of this glitch?