Re: [xine-devel] Can xine on unix work without calling XInitThreads?

[fabrizio n. <fnu...@vr...>]

Christoph (and all the others who are helping me).
I'm intersted in knowing extacly why calling XInithThread is mandatory.
It it only related to calls to the XLockDisplay and XUnlockDisplay 
primitives? Are there any other issues?

I explain my stategy in detail.

I'm able to get from the java windowing system (AWT) the pointers to 
both a valid "screen *" connection and a "drawable *" to the rendering 
surface. That's all I need to setup xine with XINE_VISUAL_TYPE_X11.

However, Java doesn't initialize the X threading system. In so doing,
XLockDisplay and XUnlockDisplay do nothing. As documented, these are 
uneffective if XInitThreads hasn't been called.
In fact, when using the player in conjunction with other AWT components, 
i quickly get on the console Xlib errors about unsynched messages and 
replies.

Proposed solution:
Use the XINE_VISUAL_TYPE_X11_2 rendering system which allows to override 
the default locking primitives (XLockDisplay and XUnlockDisplay). They 
should be replaced with calls to AWT_Lock and AWT_Unlock.


What's your opinion? Can it work?

I hope to find some free time during this week to start coding.


thanks in advance,
Fabrizo Nunnari



James Courtier-Dutton ha scritto:
> Christoph Pfister wrote:
>...
> 
> Whether to call XInitThreads or not depends on which video out plugin
> you are using. If you could write a xine-lib video out plugin that
> renders the output to some java supported window api, you should be
> fine. I don't know much about java, but I assume that a video player
> written solely in java would have some java based video display api.
> 
> James
>