On Thu, May 17, 2001 at 04:00:45PM +0200, S�bastien M�trot wrote: > There mmay be a solution GUI wise in the multithreaded model: > You can have each gui in a thread with its own select loop and XWindow My understanding is that a given process can only have one connection to the X server, and several toolkits cannot share one connection. > I got no answer about the driver server model I proposed earlier. Was it > really THAT stupid? ;-) Its just not very versatile. I imagined that would be a first step too, but if we can go straight for a proper inter-app architecture then great. - Steve
- [linux-audio-dev] More LAAGA thoughts Steve Harris
- [linux-audio-dev] Davis votes for MP, news at 11 Paul Davis
- Re: [linux-audio-dev] Davis votes for MP, news a... S�bastien M�trot
- [linux-audio-dev] gui/thread/toolkit issues Steve Harris
- [linux-audio-dev] gui/thread/toolkit issues Paul Davis
- Re: [linux-audio-dev] Davis votes for MP, news a... Steve Harris
- Re: [linux-audio-dev] optimization / restric... n++k
- Re: [linux-audio-dev] optimization / res... Karl MacMillan
- Re: [linux-audio-dev] optimization / res... D. Stimits
- Re: [linux-audio-dev] optimization / res... Yann Orlarey
- Re: [linux-audio-dev] Davis votes for MP, ne... Paul Davis
- Re: [linux-audio-dev] LAAGA restrictions Steve Harris
- Re: [linux-audio-dev] LAAGA restric... Paul Davis
- Re: [linux-audio-dev] LAAGA res... Steve Harris
