Message Box: is it cleared upon code execution?

rozek · Post by **rozek** » Thu Jun 19, 2008 8:17 am

Hello!

I just wasted some time looking for an error which didn't exist: I wrote "openStack" into the command line, pressed return and got the error message "can't find handler"

After some (unsuccessful) debugging, I had the idea to "put empty into msg" first and then "openStack" - et voila, no error message appeared!

Before, I thought that the output area of the Message Box would be cleared upon command execution - but that seems wrong?

rozek · Post by **rozek** » Thu Jun 19, 2008 8:26 am

Hmmm,

when RR did not allow me to apply changes to a script claiming there would already be a handler running (even after interrupting everything and using the Message Watcher to check that there weren't any pending messages) I decided to shut RR down and start over again.

Then, everything worked as expected (i.e., no error message was issued)

RR might have gotten confused by all my experiments

Sorry for having bothered you!

Mark · Post by **Mark** » Thu Jun 19, 2008 8:44 am

Hi Andreas,

Probably, you didn't notice that the error dialog was displaying a new error, which you had not clicked away yet.

Best,

Mark

rozek · Post by **rozek** » Thu Jun 19, 2008 8:48 am

Indeed,

this sometimes happens (although not in the case mentioned above). Even "normal" toplevel windows may hide the error dialog! (not talking about palettes or system palettes)

Is there a way to tell RR to always show the error dialog above other windows?

Mark · Post by **Mark** » Fri Jun 20, 2008 11:30 pm

Hi Andreas,

No, there isn't, because we got fed up with locked up IDE's and being unable to save our work :-) However, I believe that the error dialog appears on top of all other stacks when the error occurs. If you click on another window, it may disappear behind that window. Just make sure to click on the Ignore, Script or Debug button before doing anything else.

Best,

Mark

rozek · Post by **rozek** » Sun Jun 22, 2008 7:42 am

Hmmm,

my impressions are different - but that might be because I already clicked somewhere else before the error dialog was opened. Upon emptying the event queue, the error dialog wasn't the topmost window any longer.

From time to time, I have a similar situation under Windows itself.

Mark · Post by **Mark** » Sun Jun 22, 2008 3:21 pm

Hi Andreas,

Sometimes, you might want to execute

modeless stack "revErrorDisplay"

from the message box, to show the error window.

Best,

Mark