| Re: MESSAGE (used in VM) invokes DIALOG_MESSAGE: Can this be suppressed? [message #88404 is a reply to message #88403] |
Tue, 22 April 2014 10:44  |
chris_torrence@NOSPAM
Messages: 528
Registered: March 2007
|
Senior Member |
|
|
On Tuesday, April 22, 2014 11:07:10 AM UTC-6, Edward Hyer wrote:
> On Monday, April 21, 2014 3:25:59 PM UTC-7, Chris Torrence wrote:
>
>> Okay, I've tracked this down
>
>
>
> 1) At this point, we should take a breath and think about what users might want. I expect that people developing pure GUI apps might rely on the DIALOG_MESSAGE() behavior. There just needs to be a way to suppress it.
>
>
>
> 2) A CATCH block might solve my immediate issue. Can I have a single CATCH block that will affect all of my subroutines, or do I need to copy the catch block into each subroutine?
>
>
>
> Thanks for hunting this down!!
>
>
>
> --Edward H.
Hi Edward,
You just need to have a catch block at the top-most level of your program. For example, if everything starts out in a single routine, then you can just put the single catch there (and make sure every subroutine has on_error,2). However, if you have a widget app with event handlers, then each event handler needs to have its own catch.
-Chris
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
