Ramon van Handel wrote: > What do you suggest ? clone() and then handle Xlib updates in a different > thread ? That should work. I hope you're not suggesting calling clone from withing the signal handler though. Create the thread first, have it go to sleep, have the signal handler wake it up, let it do its work, and then go back to sleep. Or move all the processing into one thread using some sort of select model. Can be ugly, but this is of course the classic Unix (pre-threads) approach.
- Another thing about Xlib Ramon van Handel
- Re: Another thing about Xlib Jeffrey B. Siegal
- Re: Another thing about Xlib Ramon van Handel
- Re: Another thing about Xlib Jeffrey B. Siegal
- Re: Another thing about Xlib Jeffrey B. Siegal
- Re: Another thing about Xlib Ramon van Handel
- Re: Another thing about Xlib Ramon van Handel
