avoiding prepare-xwindow-id and gdk threads

[Sebastian Dröge]

On Fr, 2013-11-29 at 13:42 +0200, Dan wrote:
> OK, thanks again. One last question: how urgent is it for the app to
> take action on receiving prepare-xwindow-id? What does gstreamer do if
> I don't call imagesink.set_xwindow_id() "soon enough"? Could I call
> set_xwindow_id() from an idle_add() callback(*)?
> 
> (*) which *seems* to schedule events for the main thread, though I can
> find no definitive either GTK or PyGTK documentation stating this.

Well, if you're too slow the sink might create a window on its own or
crash :) If you do it from an idle callback it will happen sooner or
later that you're too slow, so don't do that.

-- 
Sebastian Dröge <sebastian at centricular.com>
Centricular Ltd - http://www.centricular.com
Expertise, Straight from the Source
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 966 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20131129/e1d85d3c/attachment.pgp>