comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » 5.0 XMANAGER problem
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
5.0 XMANAGER problem [message #11711] Tue, 05 May 1998 00:00
Russ Welti (on mapper is currently offline  Russ Welti (on mapper
Messages: 9
Registered: January 1998
Junior Member
I am using XMANAGER, CATCH=0, /NO_BLOCK as the final
xmanager call for my app when it begins processing user
events.

The effect of this is that the IDL engine can still be
used from the IDL> prompt even though events are being
processed. (I find this extremely convenient during development,
since I don't need to ctrl-C to get IDL's attention to .RUN a changed
source file.)

I use the /JUST_REG keyword for any additional dialogs
that need to come up later on in my app, so that the original
XMANAGER, CATCH=0, /NO_BLOCK stays in control.

However certain IDL dialogs, for example XDISPLAYFILE and
XFONT to name two, seem to just call XMANAGER with no
options, and therefor the 5.0 XMANAGER begins CATCHing
and BLOCKing and the effect is that even AFTER you dismiss
the XFONT dialog, control does NOT resume after the
call to XFONT, but rather gets locked up in event processing,
even though it was not finished processing the event which
called XFONT.

example:

begin ; event handler
f=xfont()
print,f <== this never executes, control hangs in XFONT's XMANAGER
even though OK or Cancel has been pressed and XFONT is gone.
end ; event handler


------------------------------------------------------------ --------
In short, by changing the way XMANAGER works, there has been created
a new class of problems whereby *already existing, embedded* calls
to XMANAGER (inside RSI-supplied routines) may or may not
be compatible with the CATCH and BLOCK strategy of the
user's calling application.
------------------------------------------------------------ --------

Can anyone shed light on this or tell me how to get around it,
other than do what I have had to do already in IDL: copy the
"official" version of XXX.PRO to my local IDL source directory
and create my own version of it...?

thanks,
russ

/
Russ Welti /-\
(c-g)
University of Washington \-/
Molecular Biotechnology /
PO Box 357730 /-\
Seattle, WA 98195 (a-t)
rwelti@u.washington.edu \-/
(206) 616 5116 voice (206) 685 7301 FAX /
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Re: WRONG RESULTS WITH IDL
Next Topic: about moderation and comp.lang.idl*

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Oct 08 18:38:26 PDT 2025

Total time taken to generate the page: 0.00538 seconds