avoiding prepare-xwindow-id and gdk threads

[Dan]

>> 			gtk.gdk.threads_enter()
>> 			imagesink.set_xwindow_id(self.movie_window.window.xid)
>> 			gtk.gdk.threads_leave()

> You could get the XID of the window before starting the pipeline, store
> it in some variable and then just set that when you receive the message.

So the imagesink.set_xwindow_id(somevalue) operation itself is not problematic?

> The only thing you should not do is to get the XID from the window from
> the sync bus handler. That's what requires gtk.gdk.threads_enter/leave

OK, thanks. This puzzles me though. Isn't the window.xid an XWindow
property which is set at window creation time?


Best,
Dan