[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Wed, 2006-05-17 at 12:52 +0200, Elias Pschernig wrote:
> On Wed, 2006-05-17 at 10:24 +0200, Milan Mimica wrote:
> > Elias Pschernig wrote:
> > > Ok, since it seems the XLOCK/XUNLOCK removal would go to far, I guess we
> > > should at least add the attached patch for now. It can be disabled by:
> >
> > This also means we won't get a single async reply error any more even if
> > we forget XLOCK/XUNLOCK somewhere, doesn't it?
> >
>
> Yes - but the same would be true if XLOCK would use XLockDisplay instead
> of the pthreads lock, since all X11 functions internally call
> XLockDisplay.
>
> If it seems to be a better idea, I can also make a patch to use
> XLockDisplay in XLOCK. And it could still be configurable at compile
> time via a configure parameter.
>
I committed the original one-line patch for now.
--
Elias Pschernig