Re: Xlib : sequence lost (0x1718e 0x71a0) in reply to 0x0!

2006-02-06 Thread niranjan
Hi to all I have made separate display connection to Xserver for each thread but this is working fine sometimes not always .sometime it fail when i invoke the dialog . can anybody help me to resolve this issues . Thanks Each call to XOpenDisplay opens a new

Re: Xlib : sequence lost (0x1718e 0x71a0) in reply to 0x0!

2006-02-03 Thread niranjan
Hi Thanks for quick reply. I have did according to ur suggestion call to XOpenDisplay for the new thread . But again it is working fine sometime . This is code, that I have did . *dpause (void *arg) { display = XOpenDisplay ( 0 ); pausem *paused_dialog = new pausem

Re: Xlib : sequence lost (0x1718e 0x71a0) in reply to 0x0!

2006-02-03 Thread Mark Vojkovich
Each call to XOpenDisplay opens a new communication socket to the X-server. Commands sent through this socket need to be serialized. If you have two threads trying to send data at the same time through the same socket they will corrupt each other's data. XInitThreads enables a lock around the

Re: Xlib : sequence lost (0x1718e 0x71a0) in reply to 0x0!

2006-02-02 Thread niranjan
Hi thanks for replying quickly What do you mean by separate display connections ? The case is this : I mean a display connection returned by XOpenDisplay. Thanks u have given a good suggestion but I dont understand if the pausing thread block any other thread trying

Re: Xlib : sequence lost (0x1718e 0x71a0) in reply to 0x0!

2006-02-02 Thread Tim Roberts
[EMAIL PROTECTED] wrote: What do you mean by separate display connections ? The case is this : I mean a display connection returned by XOpenDisplay. Right. I think what Carsten is saying is, if you might need to pause a thread in the middle of Xlib, then that thread needs to

Re: Xlib : sequence lost (0x1718e 0x71a0) in reply to 0x0!

2006-02-01 Thread The Rasterman
On Tue, 31 Jan 2006 22:36:23 -0800 (PST) [EMAIL PROTECTED] babbled: Hi to all Iam building an kde Application When I pause the current pthread and invoke an dialog in another thread the following error is coming . application is using the same x display connection from multipel

Re: Xlib : sequence lost (0x1718e 0x71a0) in reply to 0x0!

2006-02-01 Thread Mark Vojkovich
Separate threads either need to use separate display connections or you need to enable thread mutexes for a shared connection (XInitThreads will enable Xlib's internal mutexes). Note still, that pausing a thread while it's in Xlib can block any other threads also trying to use Xlib with the

Re: Xlib : sequence lost (0x1718e 0x71a0) in reply to 0x0!

2006-02-01 Thread niranjan
Hi u have given a good suggestion but I dont understand if the pausing thread block any other thread trying to use the Xlib with the same display connection then why it is working fine sometimes . Thanks Separate threads either need to use separate display connections or you need

Re: Xlib : sequence lost (0x1718e 0x71a0) in reply to 0x0!

2006-02-01 Thread The Rasterman
On Wed, 1 Feb 2006 22:18:49 -0800 (PST) [EMAIL PROTECTED] babbled: Hi u have given a good suggestion but I dont understand if the pausing thread block any other thread trying to use the Xlib with the same display connection then why it is working fine sometimes . Thanks that's