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

Home » Public Forums » archive » Re: IDL 5.0 widget bug?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: IDL 5.0 widget bug? [message #11115] Wed, 11 March 1998 00:00
davidf is currently offline  davidf
Messages: 2866
Registered: September 1996
Senior Member
Russ Welti (on mapper) (rwelti@mapper.mbt.washington.edu) writes:

> I'm tracking down a application freeze-up in my 4.0->5.0
> ported IDL app. (The app is FINE in 4.0 but 5.0 is causing
> headaches, crashes and freezes.)
>

> Note: this is in the KILL_NOTIFY callback of a top level
> base which is being killed due to the window manager's close
> menu pick under Solaris 2.5. The widget has already disappeared
> from the screen when the first /valid returns true above!
> (attempts to /show or /map it fail. it seems quite INvalid)

Although the IDL manual warns you many times in many places,
I don't think it gets its point across at all well. But here
it is again. Do NOT use Kill_Notify on a widget that is
being DIRECTLY managed by XManager. It results in weird and
unpredictable behavior (e.g., see the program above).

Use the CLEANUP keyword on the XManager call to assign
a Cleanup routine (exactly LIKE a Kill_Notify routine,
except that it doesn't cause these problems) for widgets
directly managed by XManager.

Cheers,

David
-----------------------------------------------------------
David Fanning, Ph.D.
Fanning Software Consulting
E-Mail: davidf@dfanning.com
Phone: 970-221-0438
Coyote's Guide to IDL Programming: http://www.dfanning.com/
[Message index]
 
Read Message
Previous Topic: functions considered as variables
Next Topic: Level 1B

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

Current Time: Fri Oct 10 17:49:39 PDT 2025

Total time taken to generate the page: 0.00680 seconds