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

Home » Public Forums » archive » IDL base widget question.
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
IDL base widget question. [message #644] Sun, 13 December 1992 22:31
turgeon is currently offline  turgeon
Messages: 3
Registered: December 1992
Junior Member
Greetings,

I am currently writing IDL widget applications. RSI does not
recomment to use the keywords XSIZE, YSIZE, XOFFSET and YOFFSET when
used with a standard base widget since they are inflexible from
platform to platform.

However, the use of these keywords is sometimes very useful. For
instance, when you wish to confirm an option after the user presses
a button in a typical application. Under X, the confirmation widget
would appear near the pressed button; the precise location is determined
by the programmer through the XtTranslateCoords(toplevel) and the NtXx
and NtNy values of the XtVaSetValues(child). By setting the NtNx and NtNy
values, one can position the child close to the parent.

In IDL, however, I don't know how to do this. How can you retrieve
the pointer position of widget types other than WIDGET_DRAW ? For instance,
how do you retrieve the pointer location after a BUTTON event is returned,
so that you can realize the child at NtNx and NtNy ?

Finally, how do you get rid of the TITLE on a base widget ? Setting
the keyowrd TITLE to "" when declaring a base widget produces a title
like "idl"... Setting TITLE to " " still gives you a title bar...

Thanks in advance,

- Ben

P.S. I am running IDL V2.3.1 with SunOS 4.1.2 on a SPARC with X11R4 and TWM.
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Mapping and registering images with IDL
Next Topic: Re: IDL base widget question.

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

Current Time: Wed Oct 08 15:36:25 PDT 2025

Total time taken to generate the page: 0.00452 seconds