From: John M. <tt...@te...> - 2004-12-20 19:49:46
|
On Mon, 2004-12-20 at 20:33 +0100, Michael Roitzsch wrote: > Hi, > > > > > I added an expose event after we go to fullscreen, didn't fix it. Even > > > > if I were to remove the double-buffering as John advised. > > > > > > I don't know gtk, but I guess you do the fullscreen by calling some > > > functions of it. Maybe the actual switch to fullscreen is not done until > > > gtk reenters its event loop? This way, you would actually send the expose > > > before the switch. > > > > > > It is clear that xine-lib needs to be notified with an expose about the > > > change in window visibility, and since subsequent exposes work correctly, > > > some "race condition" like that might be happening here. > > > > This doesn't explain why xine-lib isn't updating when a context menu > > disappears. > > Does the updating work, when you place another X window on top of totem's > video output and close it? No the video window is completely black. The expose event is sent to xine but xine isn't doing anything with it. Bastien's comment that it seems to be 1 step behind is also consistent. -- John McCutchan <tt...@te...> |