On Fri, Jan 07, 2005 at 11:10:41AM -0600, [EMAIL PROTECTED] wrote:
> FVWM Bug Tracking notification
> 
> new message incoming/1550
> 
> Message summary for PR#1550
>       From: [EMAIL PROTECTED]
>       Subject: Working Area breaks with GNOME & Xinerama
>       Date: Fri, 7 Jan 2005 11:10:09 -0600
>       0 replies       0 followups
> 
> ====> ORIGINAL MESSAGE FOLLOWS <====
> 
> >From [EMAIL PROTECTED] Fri Jan 07 11:10:20 2005
>
> SNIP 
> 
> I use FVWM as the GNOME window manager. Crazy, I know, but it works great.

This is not so crazy, we have work a lot so that can be possible.

> When I switched to Xinerama (actually NVIDIA TwinView, but it looks like
> Xinerama to X clients) the GNOME panel started getting covered by new
> windows. I believe this is because the Working Area is not being adjusted
> properly according to the _NET_WM_STRUT hints. 
> 
> SNIP
> 
> $ xprop | grep STRUT # top panel
> _KDE_NET_WM_FRAME_STRUT(CARDINAL) = 0, 0, 0, 0
> _NET_WM_STRUT_PARTIAL(CARDINAL) = 0, 0, 34, 0, 0, 0, 0, 0, 1280, 2559, 0,
> 0
> _NET_WM_STRUT(CARDINAL) = 0, 0, 34, 0
>
> SNIP 
> 
> Again, things worked fine with only one screen. If I use "EwmhBaseStruts 0
> 0 34 34" behavior is as before but because the panels only span one screen,
> I lose 68 pixels of useful mapping space on the left screen.
> 

Yes, fvwm does not support _NET_WM_STRUT_PARTIAL. So your report is a valid
bug (or a miss feature). I do not know when we will have the time to fix it.

Thanks, 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]

Reply via email to