[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
1480.0. "XSelectAsyncEvent problems in V2 FT2" by BODONI::SHERMAN () Fri Sep 22 1989 14:38
My system just got updated to V2 FT2 and my once-working application
is now having problems with Asynchronous Events. I define the event
via a call to XSelectAsyncEvent...
XSelectAsyncEvent(the_display,XtWindow(my_dialog_box_widget),
Expose,my_callback_routine,4);
where 4 is the user argument to be passed to my callback routine when
the dialog box becomes exposed. My callback routine looks like..
static
my_callback_routine(user_arg)
int user_arg;
{
...
}
Before the software update, user_arg was correctly getting the
value 4 when my_callback_routine() was called. Now it gets the
hex value 0x7ff2d000 !!! This happens for both Expose events and
ButtonPress events. Has anyone else seen this behavior or am I
doing something wrong? Perhaps someone has an XSelectAsyncEvent
sample that works under V2 FT2.
Thanks,
Mark
p.s. - All modules were re-compiled, re-UILed and re-linked.
T.R | Title | User | Personal Name | Date | Lines |
---|
1480.1 | known bug | STAR::FERGUSON | Jim Ferguson - VMS Development | Fri Sep 22 1989 15:07 | 4 |
| This is a known problem that will be fixed in the SSB version
of DECwindows V2.
|