[smallmac]

Hello. I am upgrading to WM-pro after being frustrated with WM-standard. To save me from more days of experimenting, can someone please tell me if WM-Pro can solve the following problems?

I use WM to help me play online games. I can easily program WM to choose certain game windows from another program, open that window for 15 minutes, then close it, etc. The problem...

Inevitably, a certain game is no longer available (they come and go) or there is an internet disconnection, or the game window simply fails to open... Result is that Workspace Macro shuts down because it "can't find window..."

If WM would just go on to the next click-sequence as programmed--no problem! OR... if WM would shut down every window on the desktop, then shut down--so it could restart fresh--no problem! Instead, with WM-standard, the macro just stops in the middle. And it cannot restart, because then it trys to open the master program that is already open. And that causes error messages, etc.

So I need either....

a. If the macro does not find a window to close... just proceed to next click sequence (which will tell it to close the main window)... do not stop...

...Or...

b. Before running the main macro every hour, run another macro that "finds every window that is open and closes it, regardless of what it is." (Then I can be sure that if anything goes wrong, all the error windows will be closed and within an hour, the macro will be running again with a clean slate.)

Can this be done with WM-pro? Thank you anyone.

...P.S...

Some windows fail to close for no apparent reason. Sometimes it works, sometimes it doesn't. But I seem to be making headway by "scheduling" the macros. I make the main macro 27 minutes, and run every 30 minutes starting at 00.00.00 hours every day. (This requires using the Windows XP control panel to modify further the "schedule" that is produced by Workspace.) Then I made 2 separate extra "window-closer" macros, every 30 minutes, starting at 00.28.00 hours and 00.29.00 hours.

It is a bit comical because if the "smart macro" cannot find the window it is supposed to close--i.e., if the closing is not needed because the window closed properly in the main sequence--then for one program, the macro reopens the window so that it can close it. I did not expect this and I hope all these 48 extra opens and closes daily don't wear something out...! So far this works.

But can the pro version be told not to reopen the window if it is already closed...?

(For the other program--if the window is not found open, the macro produces a temporary error message, "Can not find program..." This is more what I expected and is no problem at all.)