discuss-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fwd: Re:


From: copal
Subject: Fwd: Re:
Date: Sun, 7 Dec 2003 22:30:16 -0600

it's not that this is an atom that IWM can't ignore, it's that this is an atom that is being used to identify the GNUstep menus instead of a standard EWMH atom; before i added this atom to IWM and included it in the method that detects what kind of decor to add to the client (in this case, a menu), the window shows up incorrectly.

- ian


4. As a TEMPORARY SOLUTION, added a ***KDE*** window type atom to the
-initializeEWMHDecorations method to resolve problems with GNUstep menus. This is an issue that needs to be resolved within the GNUstep backend, not InterfaceWM. But until the EWMH window type is set to spec, this will be
the only way for GNUstep menus to behave properly under Interface.

I don't quite understand why this workaround is needed. According to the
EWMH specification a window manager should just ignore type atoms it
does not know (in this case the KDE one) and use the next atom instead.
Or am I missing the real problem here?






reply via email to

[Prev in Thread] Current Thread [Next in Thread]