Re: [xine-devel] synchronous xlib access

[Christoph P. <chr...@gm...>]

Am Samstag, 28. Oktober 2006 21:15 schrieb Miguel Freitas:
> On 10/28/06, Christophe Thommeret <hf...@fr...> wrote:
> > Le Samedi 28 Octobre 2006 21:03, Miguel Freitas a =E9crit:
> > > On 10/28/06, Christoph Pfister <chr...@gm...> wrote:
> > > > Bah, your mail box really seems to ignore certain mails ;)
> > >
> > > huh?
> >
> > Quoting Christoph:
> >
> > Bah, I'll give that up (after >70kb patch) and let xine run in a sepera=
te
> > process.
> > The biggest problem I see is that you nearly nowhere have to call
> > X*LockDisplay directly (because most x functions call it internally -
> > using a recursive mutex). Especially for xvmc there were too much lock /
> > unlock missing for my taste.
> > So I can just hope that there will be a better xlib mt concept in the
> > future ...
>
> i saw that message, but i guess i misunderstood it: i thought he gave
> up because the amount of changes (but what i commited must be less
> than 20kb).

70kb included most output plugins.

> anyway, patch is now on cvs and will be included in 1.1.3.
>
> Miguel

It won't be that easy for all plugins - e.g. for xvmc i expect some=20
trouble ... but now when this solution seems tangible i must admit that i=20
consider it as less effort than to let xine run in a seperate process ...

Christoph