View System Windows Locks Macro Scheduler

mhortman · Post by **mhortman** » Mon Jan 15, 2007 1:34 am

I think the Subject says it all. Macro Scheduler becomes unresponsive and has to be killed via task manager. I tried to write my first macro and it had only two lines the first was GetWindowText - > found a good window gave it a variable, then tried to message the variable, that locked the sucker up also.

Thanks.

pgriffin · Post by **pgriffin** » Mon Jan 15, 2007 2:15 am

Are you saying that you opened View System Windows, then ran a macro with ViewSystem Windows still open and it locked up?

Haven't encountered this myself, but were you able to close ViewSystemWindows and then run a macro successfully?

mhortman · Post by **mhortman** » Mon Jan 15, 2007 3:46 am

Well, first off if I am in the macro editor, and go to tools, View system windows, the program locks up.

Second. if I write a macro and it contains only the command GetWindowText it also locks up.

Bob Hansen · Post by **Bob Hansen** » Mon Jan 15, 2007 4:40 am

The syntax is GetWindowText>window_title,text

Can you show what you are using?
What ends up in the variable for text?

mhortman · Post by **mhortman** » Mon Jan 15, 2007 4:59 am

Nothing shows up , it just locks up.

It also locks up in the macro editor Tool->ViewSystemWindows though, so I strong suspect that it is not my syntax.

bnc1 · Post by **bnc1** » Mon Jan 15, 2007 6:00 pm

By any chance are you using Nvidia's Nview Desktop Manager ? I had a similar problem with code FindWindowWithtext and also when using View System Windows from the editor. I posted it awhile back

http://www.mjtnet.com/forum/viewtopic.php?t=2467

Bob Hansen · Post by **Bob Hansen** » Mon Jan 15, 2007 9:56 pm

If you post the script you are using, it may be easier for us to help you.

Provide the line that fails and a few lines above and below it.

mhortman · Post by **mhortman** » Mon Jan 15, 2007 10:11 pm

bnc was onto the problem. It was the fact that I had a desktop manager running, not Nviews, but when I killed it, it is now running the command.

Way Cool.

Thanks for the help