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

Home » Public Forums » archive » IDL widgets: comments and questions
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 widgets: comments and questions [message #3829 is a reply to message #3752] Fri, 17 March 1995 01:27 Go to previous messageGo to previous message
cannon is currently offline  cannon
Messages: 1
Registered: March 1995
Junior Member
In article <3k7396$6qi@hermod.uio.no>, steinhh@amon.uio.no (Stein Vidar Hagfors Haugan) writes:
|>


|> If you set it up correctly using a tree structure, you only need
|> one widget ID in order to find your information no matter how complex
|> your application is. The places where you have a legitimate
|> need for that ID is inside the event handler (or routines called by the
|> event handler). And in the event handler, you do have EVENT.TOP
|> (and even EVENT.HANDLER/EVENT.ID!). This, in combination with structure
|> variables as UVALUES, removes any need for common blocks in order
|> to pass data anywhere.
|>
.... cut ....


I'm trying to adopt your philosophy, but how do you handle a function
which uses a widget to return a value (like the pickfile routine say,
which uses a common block)? You call the function which creates the
widgets and it is all fine until you want to exit, with the value you
want the function to return in a uvalue somewhere. But to exit you
have to destroy the widgets so control gets handed back to the function
which made them - and then it cant get at the uvalue any longer to return
the thing you want??

The only examples i've seen use common blocks, but is there any other way
round it?


Robert Cannon
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Can I prevent Widget List Re-sizing?
Next Topic: Re: freeing memory in programs

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

Current Time: Fri Oct 10 21:50:12 PDT 2025

Total time taken to generate the page: 0.72837 seconds