I think this whole threads thing is "barking up the wrong tree". If I recall
correctly the issue is getting notified of some sort of event, which we happen
to be doing differently depending on whether threads are involved. I think I
looked into this and concluded that we could do it with an XtEvent handler,
however I got lost in the #if X11R6 vs. X11R5 macros that we have in Vendor.
Both cases where doing essentially the same thing, but in different ways, then
something else came up, and I don't have any R5's to check things
against.......Bottom line, I don't think threads was the main issue here..
On 02-Aug-00 at 20:34, Alexander Mai ([EMAIL PROTECTED]) wrote:
> Well, I couldn't find the last thread about XTHREADS so I raise the issue
> again: one problem was that appearently we check using _XtProcessLock()
> for XTHREADed libs, why don't we use XtToolkitThreadInitialize? The first
> doesn't work on Digital un*x (and probably on others as well).
> We should finally get this done, since this would help LessTif on this
> platform very much. If I want to test it now, I always patch Vendor.c to
> get the right code selected.
>
> --
> Alexander Mai
> [EMAIL PROTECTED]
>
>
