Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!ucbvax!tut.cis.ohio-state.edu!bloom-beacon!TUB.BITNET!net
From: net@TUB.BITNET (Oliver Laumann)
Newsgroups: comp.windows.x
Subject: Re: Patch number 9
Message-ID: <8903301615.AA23759@tub.UUCP>
Date: 30 Mar 89 16:15:02 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 19

>     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