On Fri, Nov 23, 2001 at 11:18:55AM +0100, Dominik Vogt wrote: > On Thu, Nov 22, 2001 at 04:04:51PM -0600, fvwm-workers wrote: > > CVSROOT: /home/cvs/fvwm > > Module name: fvwm > > Changes by: olicha 01/11/22 16:04:51 > > > > Modified files: > > . : ChangeLog acconfig.h configure.in > > fvwm : ConfigFvwmDefaults Makefile.am add_window.c > > bindings.c events.c ewmh.c ewmh.h ewmh_events.c > > ewmh_icons.c ewmh_intern.h functions.c > > functions.h fvwm.c fvwm.h fvwm2.1 placement.c > > screen.h session.c style.c update.c update.h > > window_flags.h > > libs : Bindings.c Picture.c Picture.h fvwmlib.h > > > > Log message: > > * Remove most of the ewmh ifdef > > * New commands EWMHBaseStrut and EWMHNumberOfDesktops > > * Some minor ewmh fixes > > * Warning: document the new commands and more doc in the ewmh section. > > I noticed a macro IS_EWMH_DESKTOP() in the code. Do I understand > it correctly that the virtual root window of KDE is stored in a > regular FvwmWindow structure?
Yes, there is also a new context for this type of application: 'D'. > Wouldn't it be easier then to give > it a special treatment so that we don't need these IS_EWMH_DESKTOP > checks all over the place? > The point is that it should be managed by fvwm (at least for bindings and other small things). Then, we need to know its "fvwm" parent for computing the 'D' context, so I use a full FvwmWindow structure for it (and not just a window id, but this is probably possible). In any case I do not see how to remove all these IS_EWMH_DESKTOP check without going into a lot of problems. Olivier -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
