On Thu, Aug 08, 2002 at 08:20:41AM -0500, fvwm-bug wrote: > FVWM Bug Tracking notification > > new message incoming/912 > > Message summary for PR#912 > From: [EMAIL PROTECTED] > Subject: _NET_WM_DESKTOP ignored for initial placement > Date: Thu, 08 Aug 2002 08:20:40 -0500 > 0 replies 0 followups > > Full_Name: Matthias Clasen > Version: > CVS_Date: > OS: > X_Server: > Submission from: (NULL) (195.243.100.246) > > > Metacity recently started handling the WM_Sn manager selection, so I > took the opportunity to test the handshaking between metacity and fvwm > 2.5.2. > Works nice in general, but for one thing: > > When fvwm takes over from metacity, it seems to ignore the _NET_WM_DESKTOP > properties left behind by metacity. Worse, windows which are not on the > first desk sometimes get completely lost - they don't appear on any desk, > but switching back to metacity makes them reappear at the right position.
Could you point me to the spec and the specific place that states how the _NET_WM_DESTOP property should be handled? I'd assume the window manager is resposible of deleting this property from the client window and map all windows on all desks when it terminates. How else should the WM find out about windows that are not mapped when it starts and that are never mapped by the application? Bye Dominik ^_^ ^_^ -- Dominik Vogt, mail: [EMAIL PROTECTED], phone: 0721/91374-382 Schlund + Partner AG, Erbprinzenstr. 4-12, D-76133 Karlsruhe -- 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]
