If the script works when the window position is at 0,0 (upper leftmost) you may be able to handle different window positions by:-

1) getting the current position of the window.
2) adding those values(as variables of course) to the mouse and other positioning commands.

Support: Just in case you have an interest in resolving this issue and not have propagate further in your new versions. The computers that exhibit this problem are Pentium 1, 233 Mhz running windows 2000 or WinNT Service Pack 5. As mentioned before, this problem only happens if ‘Msg_stayontop=...

Hello All,

I am sure about the setfocus.

You understand that the problem exists in version 7.4.009. It does not exist in version 7.3.11. I do not know about the versions in between.


Kris Thayloo

I am trying to operate Roxio's Direct CD to format a CD-R disk including writing a volume ID. With Msg_stayontop=1, the commands (alt-n) to get the next screen/page are not received by Direct CD. With Msg_stayontop=0, I do not have the problem. The script flaw that I referred previously in the ver 7...

Support:- You're probably right. That version of compiler just revealed a flaw in my script that was previously appearing intermittently but is now showing up consistently ! The application that supposed to receive data was not at the proper "page" where it could accept data and consequently the dat...

I now have a problem with a recompiled but unchanged script (was previously compiled with ver 7.3.....).
It appears that focus is being grabbed by the MacroScheduler Message window. Msg_stayontop is set to 1.

thanks

Kris Thayloo

We are using macro scheduler in script form. Does anyone know if the compiled scripts ( executables) will require less resources, viz., cpu time?

This may not be what you're looking for but here goes.

How about having a script ( non exe) macro that is triggered by the xp message (wait window open). Have this macro respond to the the "do you really want to do this" message.

Kris Thayloo

I am trying to figure out how to use your suggestion Mr Hansen. ...but the following thoughts came to mind. If a wait_window closed statement were to be placed before the input/ask, then this window will not be existence for the wait statement to reference. If it were to be placed after the input/as...

Is there a way to place a time limit on user input ( ask, input). I am very much in need of this feature. I need the script to continue execution if the user makes no input after some specified time. Right now there is just and indefinite wait.

Thanks