Re: widget_control, event.TOP, /destroy [message #48925] |
Thu, 01 June 2006 09:55 |
Nikki Bloms
Messages: 7 Registered: December 2005
|
Junior Member |
|
|
Thank you Benjamin, works like a charm.
Nikki
Benjamin Hornberger wrote:
> Even after destroying the widget base, the event handler will continue
> (you might want to clean up something, etc.). You have to explicitely
> put a RETURN statement after destroying the widget base.
>
> Benjamin
|
|
|
Re: widget_control, event.TOP, /destroy [message #48926 is a reply to message #48925] |
Thu, 01 June 2006 09:54  |
Nikki Bloms
Messages: 7 Registered: December 2005
|
Junior Member |
|
|
Thank you Benjamin, works like a charm.
Nikki
Benjamin Hornberger wrote:
> Even after destroying the widget base, the event handler will continue
> (you might want to clean up something, etc.). You have to explicitely
> put a RETURN statement after destroying the widget base.
>
> Benjamin
|
|
|
Re: widget_control, event.TOP, /destroy [message #48931 is a reply to message #48926] |
Thu, 01 June 2006 08:24  |
Benjamin Hornberger
Messages: 258 Registered: March 2004
|
Senior Member |
|
|
Nikki Bloms wrote:
>
> errormsg = dialog_message(msg, /center, /question, title=$
> 'Please pick a set of DICOM files')
> CASE errormsg OF
> 'Yes': ;---retrieves filepath of select dicom files
> 'No': widget_control, event.TOP, /destroy
> ENDCASE
>
> The next item in the event code is the creation of a dicom object from
> the selected files retrieved in case of 'Yes'. If 'No' is selected in
> the dialog_message, the code returns the following error message.
>
> "XMANAGER: Caught unexpected error from client application. Message
> follows...
> OBJ_NEW: Error: Unable to locate file (filename argument) ,"
>
> Why does the code keep progressing when I call /destroy? I've searched
> through the newsgroup archives, as well as the Online Help and haven't
> really found anything that might explain this.
Even after destroying the widget base, the event handler will continue
(you might want to clean up something, etc.). You have to explicitely
put a RETURN statement after destroying the widget base.
Benjamin
|
|
|