net@TUB.BITNET (Oliver Laumann) (03/30/89)
The recently posted official patch number 9 fixes the problem that XtAddConverter() adds the converter to the wrong application context; however, the problem remains for timers and probably also for work-procs. XtAddTimeOut() adds the timer to the default application context, no matter which application context is actually used by the application. This causes certain widgets (e.g. the HP scrollbar widget) to not properly work when the application makes use of an explicitly created application context. Regards, -- Oliver Laumann net@TUB.BITNET net@tub.UUCP
rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (03/30/89)
XtAddTimeOut() adds the timer to the default application context,
no matter which application context is actually used by the application.
This causes certain widgets (e.g. the HP scrollbar widget) to not
properly work when the application makes use of an explicitly created
application context.
XtAddTimeOut() is doing the right thing. Widgets should be using
XtWidgetToApplicationContext() to figure out what context they're in,
and call XtAppAddTimeOut() instead. Similar for work procs.net@TUB.BITNET (Oliver Laumann) (03/31/89)
> no matter which application context is actually used by the application. > This causes certain widgets (e.g. the HP scrollbar widget) to not > properly work when the application makes use of an explicitly created > application context. > > XtAddTimeOut() is doing the right thing. Widgets should be using > XtWidgetToApplicationContext() to figure out what context they're in, > and call XtAppAddTimeOut() instead. Similar for work procs. Sorry, I was confused. The bug is, of course, not in the intrinsics, but in the widget classes that are using XtAddTimeout(), in this case in the HP scrollbar widget. Should bugs in the user contributed software (such as Xhp) also be reported to xbugs@expo? Regards, -- Oliver Laumann net@TUB.BITNET net@tub.UUCP
rws@EXPO.LCS.MIT.EDU (Bob Scheifler) (03/31/89)
Should bugs in the user contributed software (such as Xhp) also be
reported to xbugs@expo?
No. (The release notes are pretty explicit on this point.)