| Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
| Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
| Moderator: | STAR::VATNE |
| Created: | Mon Oct 30 1989 |
| Last Modified: | Mon Dec 31 1990 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3726 |
| Total number of notes: | 19516 |
In the call to the high level routine, LIST_BOX, how are individual
elements of the parameter CALLBACKS mapped to the reasons defined
for the LIST_BOX widget?
For example, is the 1st element of the array always mapped to the
Single, the 2nd to Single Confirm, 3rd to Extend, 4th to Extend
Confirm?
What happens if less than 4 elements are provided in CALLBACKS
parameter?
A more general question - Is this behavior the same for all widgets?
Bill.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2261.1 | who knows? | AITG::DERAMO | Dan D'Eramo, nice person | Tue Feb 13 1990 19:31 | 10 |
Wild guess ... it calls your callback routines for any of
those reasons, and you have to check the reason (first
field in the callback data structure) to tell what
happened? I couldn't answer this question going through
the VMS DECwindows Toolkit Routines Reference Manual in
the book reader. The bindings for the callback reasons
are in the section documenting the low level create
routine.
Dan
| |||||
| 2261.2 | Use low level... | LEOVAX::TREGGIARI | Wed Feb 14 1990 07:55 | 14 | |
The callback list you provide is set on the DwtNsingleCallback,
DwtNsingleConfirmCallback, DwtNextendCallback, and
DwtNextendConfirmCallback callback lists. So the same routine (or routines)
will be called for all those "reasons". If you need finer control,
use the low-level routines.
Leo
P.S. - use the low-level routines anyway; high-level routines
aren't in Motif, and often when you use a high-level
routine, you later have to come back and change it when you
need to set an additional parameter that you can't from
the high-level routine.
| |||||