On 16 Jul 2003 21:53:37 +0200, Olivier Chapuis wrote: > > On Wed, Jul 16, 2003 at 09:21:06PM +0200, Olivier Chapuis wrote: > > On Wed, Jul 16, 2003 at 06:08:41PM +0200, Olivier Chapuis wrote: > > > > > > The problem is simple: all gnome panels have the same name, icon name, > > > res name and class name! So when we restore the window state > > > fvwm/session.c > > > is unable to make the distinction between all the gnome panels. > > > > > > Any idea for a fix? > > > > The obvious idea after reading the SM spec (and the ICCCM2) is to use > > the SM_CLIENT_ID property (on a possible WM_CLIENT_LEADER window) But, > > at first view the gnome panels have no SM_CLIENT_ID set!!
I did not notice these additional messages before writing my previous reply. I think this bug (gnome-panel does not support XSMP and does not set SM_CLIENT_ID) should be reported to gnome-panel developers. > > I think > > that sawfish, metacity, icewm and kwin simply ignore window without > > the SM_CLIENT_ID property set (on the client leader) regarding session > > management. > > > > I think we should add the SM_CLIENT_ID as the main identifier in > > the session code and either: > > Ok sorry it is already the case. > > > - do not reset "session state" for windows with an identifier > > (sm client id, name ...etc) with two matching identifiers in the > > session window list. > > or > > - simply do not save/restore state for window without SM_CLIENT_ID. Old application do not support XSMP (I think xterm already supports XSMP, but probably rxvt does not). After name comparision there is a command line comparision. So if 2 windows have the same command lines (say "xterm -ls -g 80x40") it is really not important if we replace them, since they are just indentical. I can't explain how 2 gnome-panel use the same command lines and open different panels (one at top and one at bottom). I guess one gnome-panel process opens 2 windows, at top and at bottom. I would really fix this in gnome-panel, because the current fix makes old applications (like 2 rxvt with the same parameters) to lose all fvwm properties/flags on the next session. This is only my understanding. Regards, Mikhael. -- 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]
