| Re: event fields [message #2357] |
Tue, 28 June 1994 18:29 |
rivers
Messages: 228
Registered: March 1991
|
Senior Member |
|
|
In article <bschwar2-240694095447@boson.swarthmore.edu> bschwar2@cc.swarthmore.edu (Brian Schwartz) writes:
> Can someone tell me the meaning of the IDL event fields? The Users Manual,
> pade 20-6 defines event.id, event.top, and event.handler. From context, I
> have an idea what event.value is. But there is also event.select, and
> probably some others.
Each different widget type has a different event structure which it
passes to your event handler routine. All contain the .id, .top and
.handler fields, but other fields differ from widget to widget. They
are described where each different widget type is described.
--
Mark Rivers (312) 702-2279 (office)
CARS (312) 702-9951 (secretary)
Univ. of Chicago (312) 702-5454 (FAX)
5640 S. Ellis Ave.
|
|
|
|
| Re: event fields [message #2365 is a reply to message #2357] |
Tue, 28 June 1994 01:19  |
robijn
Messages: 18
Registered: June 1994
|
Junior Member |
|
|
In article <2umumm$gqp@vulcan.giss.nasa.gov>,
Daniel M. Israel <crdmi@vulcan.giss.nasa.gov> wrote:
>
> Could someone explain event.handler? I read the manual, but I still
> don't get it.
>
event.id is the ID of the widget that sent the event, event.handler
is the widget to which the event handling function belongs. E.g.,
when you have a base widget with a lot of button widgets as childs,
you can associate an event function with the base widget only. When
a button is pressed, the base widget receives an event where event.ID
is the button that was pressed and event.handler is the ID of the base
widget. You'll need that in more complicated situations such as compound
widgets.
Frank
--
_____ ____
/ / / Frank Robijn Internet: Robijn@Strw.LeidenUniv.NL
/___ /___/ Sterrewacht Leiden Bitnet: Robijn@HLERUL51
/ / \ Phone (31) 71 275841 Local: Robijn@HL628
/ / \ Fax : (31) 71 275819 Snail: P.O.Box 9513, 2300 RA Leiden,
The Netherlands
|
|
|
|
| Re: event fields [message #2373 is a reply to message #2365] |
Mon, 27 June 1994 09:28 |
crdmi
Messages: 10
Registered: February 1994
|
Junior Member |
|
|
> Brian Schwartz (bschwar2@cc.swarthmore.edu) wrote:
> : Can someone tell me the meaning of the IDL event fields? The Users Manual,
> : pade 20-6 defines event.id, event.top, and event.handler. From context, I
Could someone explain event.handler? I read the manual, but I still
don't get it.
--
Daniel M. Israel "So you better hope there's intelligent
<crdmi@vulcan.giss.nasa.gov> life somewhere out in space, 'cause there's
Goddard Institute of Space Studies bugger all down here on Earth!"
2880 Broadway, New York, NY -Monty Python's "Universe Song"
|
|
|
|
| Re: event fields [message #2386 is a reply to message #2373] |
Fri, 24 June 1994 08:55 |
sjt
Messages: 72
Registered: November 1993
|
Member |
|
|
Brian Schwartz (bschwar2@cc.swarthmore.edu) wrote:
: Can someone tell me the meaning of the IDL event fields? The Users Manual,
: pade 20-6 defines event.id, event.top, and event.handler. From context, I
: have an idea what event.value is. But there is also event.select, and
: probably some others.
event.select is a flag in a button event from an exclusive or
nonexclusive base and indicates whether the button has just been set or
unset (1 if it was set, 0 if released). The only other field I can recall
offhand is event.button from draw widgets only which returns which button
was used to generate the event.
: Thanks,
: Brian.
--
James Tappin, School of Physics & Space Research
University of Birmingham
sjt@xun8.sr.bham.ac.uk
"If all else fails--read the instructions!"
O__
-- \/`
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
