Hello!
> What version of XCB are you using? There were a significant number of
> thread-related problems introduced when libX11 first switched to using
> XCB as a backend. I'd suggest using a libX11 built without XCB, but
> doing that has gotten a lot harder on recent distributions.
1.7
> T
On 03/12/13 12:21 PM, Aaron Plattner wrote:
> On 03/12/2013 11:52 AM, Torsten Jager wrote:
>>> Applications should never call those functions - they are Xlib's
>>> internal locking mechanism for the request buffers.
>>
>>> Applications should only call XInitThreads() to set up the locks
>>> before
On 03/12/2013 11:52 AM, Torsten Jager wrote:
Applications should never call those functions - they are Xlib's
internal locking mechanism for the request buffers.
Applications should only call XInitThreads() to set up the locks
before any Xlib calls are made.
I think Allen must have been thin
> Applications should never call those functions - they are Xlib's
> internal locking mechanism for the request buffers.
> Applications should only call XInitThreads() to set up the locks
> before any Xlib calls are made.
Thank you for answering.
You are confusing me. My manpage says
"It is o
On 03/07/2013 06:31 AM, Torsten Jager wrote:
Hello!
What is the proper usage of XLockDisplay () / XUnlockDisplay ()
when an application has multiple threads using
* "normal" Xlib functions
* Xitk functions
* libGL and/or
* libvdpau ?
XLockDisplay / XUnlockDisplay is only required
On 03/ 7/13 06:31 AM, Torsten Jager wrote:
> What is the proper usage of XLockDisplay () / XUnlockDisplay ()
> when an application has multiple threads using
Applications should never call those functions - they are Xlib's
internal locking mechanism for the request buffers.
Applications should on
