[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Peter Wang wrote:
Hmm, is this due to a deficiency in the current implementation, or is
there nothing further Allegro can do?
It seems to be a deficiency in Xlib's locking system. One would think
that when you unlock a display mutex, Xlib would automatically switch to
another thread if it was waiting on a lock.. this appears to not be the
case though. So what happens is the lock is released, then quickly
locked again by the main thread leaving little time for input and such
to be gotten. About the only thing I can think of for Allegro to do is
yield whenever XUNLOCK is called, but that would play havoc with the
rest of the program.
- Kitty Cat