responding to modal message box.

[Mechellallen]

The macroScheduler script I have is stopping once a modal message box pops up. I'm unable to send a response and/or close a window until the message is responded to outside of macro scheduler. Once I respond to the message box the macro scheduler script will continue.

[JRL]

That's pretty much the way MessageModal> is supposed to work.

From help for MessageModal>

Displays a message box containing the text specified in message_text. With this command the Message box is modal. This means that the script will not continue until OK is pressed. For non modal message boxes use Message.

If you need a message box that responds in a special way you might try creating your own message using the dialog functions. Or you could use Rain'smessage box wizard located here

Hope this helps,
Dick

[Mechellallen]

I'm not creating the modal window. I'm automating/stepping through a process that causes the modal window to pop up and am unable to close it. I've tried several different actions:

WaitWindowOpen>Generate Purchase Order
MoveWindow>Generate Purchase Order,519,421
Wait>1.06
PushButton>Generate Purchase Order,Generate
WaitWindowOpen>Message
SetFocus>Message
Press Enter

and
WaitWindowOpen>Message
PushButton>Message,OK

and
WaitWindowOpen>Message
SetFocus>Message
CloseWindow>Message

and
PushButton>Generate Purchase Order,Generate
Press Enter

[Bob Hansen]

Try adding a "*" to the end of each of the window names in your script.

For example: WaitWindowOpen>Generate Purchase Order*

What happens when you single step, where do you have a problem?Which command is triggering a modal window? What program is generating it?
Do you have a log file?

Again, Modal Windows must be responded to before you can proceed, that is normal functioning.

[Marcus Tettmar]

Try removing all PushButton statements and replacing with key sends or mouse clicks. I have seen PushButton put applications into strange states - not all of them seem to be able to cope with the button push message at that lower level, whereas simulating user input is fine.

[yenprice]

I ran into a similar situatiion. I work around it by using MouseMove and LClick the button that cause the modal window to pop up, then use MouseMove and LClick again to close the modal window. If the locations of your button and the pop-up window are static, you can use this method. If they appears at different places at different time, then FindImagePro will work.

Hope this help

[Marcus Tettmar]

I ran into a similar situatiion. I work around it by using MouseMove and LClick the button that cause the modal window to pop up, then use MouseMove and LClick again to close the modal window. If the locations of your button and the pop-up window are static, you can use this method. If they appears at different places at different time, then FindImagePro will work.

Hope this help

MouseMoveRel is another way. Moves the mouse to a position relative to the upper left position of the active window. So doesn't matter where the window is.