DIALOGS MESSAGE OFF - Odd behavior

DIALOGS MESSAGE OFF - Odd behavior

cfastNJWK6
Advisor Advisor
708 Views
2 Replies
Message 1 of 3

DIALOGS MESSAGE OFF - Odd behavior

cfastNJWK6
Advisor
Advisor

I am having an issue that I can't trace down.  I have multiple macros that turn the dialog and error messages off and back on again at the end.  Multiple users use these macros.  A problem has cropped up where a user stops receiving messages in powermill.  I get called over and I type "DIALOGS MESSAGE ON" in the command window and the problem is solved.  I wanted to write a macro that the users could click to do this on their own, but I found that the macro command doesn't work as it used to.  I found a forum post that said that the message state is returned to its initial setting before the macro is ran.  If this is true, how are my messages getting turned off and how can I write a macro to turn them back on?

0 Likes
709 Views
2 Replies
Replies (2)
Message 2 of 3

danmic7JH66
Advocate
Advocate

Typically, if someone aborts a macro after starting it the command for turning the messages off will get ran but the command to turn them back on again won't get ran. I would imagine that's what's causing your porblems.

0 Likes
Message 3 of 3

cfastNJWK6
Advisor
Advisor

I also believe that a macro is being aborted and that is what is causing my root issue.  However, how can I turn the messages back on via a macro?  I can type "DIALOGS MESSAGE ON" into the command window and that solves the problem, but running a macro with that same command only turns the messages on while the macro is running.

DIALOGS MESSAGE ON
MESSAGE INFO "Messages have been turned back on"

Running the above macro does turn the messages on (the message box saying "Messages have been turned back on" does appear.)  But, after the macro is completed the state of the dialogs messages is reverted back to what it was before the macro ran.  I tried putting this code into a function and calling the function and I get the same result.  I also tried putting MACRO ABORT after the code to try and simulate a macro ending abruptly but I still get the same result.

0 Likes