Re: [tlug] Weird problem with xine and KDE

[Godwin Stewart <gstewart@example.com>]

On Fri, 09 Jul 2004 09:38:45 +0900, "Stephen J. Turnbull"
<stephen@example.com> wrote:

> Well, now you have a workaround.  One point for the good guys.

True.

I'm still compiling KDE 3.3 beta just to see...

> Do the ConfigureNotify events stop when you hide the GUI?

Yes.

>     Godwin> Do I know which window /what/ is?
> 
> The one getting all the ConfigureNotify events.

Yes. It's the so-called "Navigator" window. Furthermore, I've just
discovered that unmapping just *that* window and leaving the rest of the GUI
in place also unsticks things.

This is probably important: the navigator window is kind of docked to the
main GUI in that it follows the GUI around when you move it. This must mean
that the main GUI is sending messages to the navigator whenever the former
moves.

> Looks like it must be the GUI, but it's worth confirming.  You can check
> that with xwininfo, which gives the window id.

That's how I found out which window I should intercept the messages for in
the first place. I tried the main GUI, the output window and the taskbar as
well as the navigator.

> Could you give me a few more of those events, in sequence?

I just get this same event repeating itself over and over again:

ConfigureNotify event, serial 20, synthetic YES, window 0x2000d17,
    event 0x2000d17, window 0x2000d17, (784,44), width 250, height 222,
    border_width 0, above 0x0, override NO

Is there a way to get the ID of the window SENDING the message?

> Alternatively, if they're all identical except for serial number, I think
> we can conclude that there's a knockdown dragout brawl over window
> configuration going on for some reason.

That's what it looks like.

> Also, can you see a flicker or anything like that in the GUI? Does the GUI
> have a dynamic display in it?

No flicker, and there's no real dynamic display - just a slider moving along
slowly, marking the elapsed time.

> At this point, I have to think that kicker or the kde library
> functions that handle window geometry are buggy.
> 
> What seems to be going on here (GNOME has similar problems) is that
> the desktop environment developers design (or maybe it's simply a
> subset of Xt) their own protocols for session and window management
> rather implement the full Xt protocol exactly.  This results in
> programs written with a different toolkit getting screwed, because
> they don't use exactly the protocol that the desktop expects.

That's possible, yes. We'll see what gives once I have KDE-3.3ß running. If
it's the same old story I'll drop the KDE guys a line. Maybe the xine guys
too - altho' last time I did that I received a ton of spam through the xine
mailing list. Looks like there's no filtering on the sourceforge.net MX...

-- 
G. Stewart   --   gstewart@example.com -- gstewart@example.com
Registered Linux user #284683 (Slackware 9.0, Linux 2.6.7-em8300)
--------------------------------------------------------------
Sign spotted in an office:
AFTER TEA BREAK STAFF SHOULD EMPTY THE TEAPOT
AND STAND UPSIDE DOWN ON THE DRAINING BOARD

Attachment: pgp00033.pgp
Description: PGP signature