How to programmatically close a message box

[Heinz57]

Hello,

my programming in MS works fine and I am implementing a sort of debug mode to give the operator / user frequent status information about what is going on besides writing this to a log file.

But when opening non-model MacroScheduler message boxes I find no way how I can close them again.

Is there something similar to IEClose related to MacroScheduler message boxes? I found nothing in the docs or in the forum.

The only way I could think of would be by via an image search and then pressing the button but that's kind of crazy and time consuming also.

Best regards
Heinz57

[Marcus Tettmar]

You can use CloseWindow:

CloseWindow>Macro Scheduler Message

[JRL]

I very often use message boxes for debugging and also just monitoring the progress of a completed script. I will often start a script with something similar to:

Code: Select all

Let>msg_xpos=10
Let>msg_ypos=10
Let>msg_width=500
Let>msg>height=300
Message>

Then as the code progresses, at points where I want to know certain variable values, I will use SetControlText> to put the information in the message box for display. For example:

Code: Select all

SetControlText>Macro Scheduler Message,TMemo,1,Cycle Count=%Cycle_Count%

You could just issue the Message> command over and over with different messages and visually get the same result. The reason to use SetControlText> is to prevent the message window from acquiring focus.

As Marcus pointed out you can programmatically close the message window using:

Code: Select all

CloseWindow>Macro Scheduler Message

Then reopen it at any time using:

Code: Select all

Message>

[Heinz57]

@Mr. Tettmar

I beg your pardon but I forgot to mention in my OP that I hat tried CloseWindow>Macro Scheduler Message before and it did not work for me.

I now used it again only to find out that the exe aborts with an error when there is no such window. Since one can never be sure if the user has closed the message box, this is no solution.

I think the only proper solution would be to return a handle when creating a box very much like in IECreate. This handle could then be used to close the box and this operation should not crash if the window had been closed before.

@JRL
Thank you for this clever proposal. I will consider using it (later, currently busy with more urgent tasks). But I currently tend to delegate this to my main application, which will soon run as the master process and start MS scripts as needed. But this will only really work with the SDK.

[Marcus Tettmar]

You could do:

Code: Select all

IfWindowOpen>Macro Scheduler Message
  CloseWindow>Macro Scheduler Message
Endif

This would only work for a NON modal message box of course.