Issue 480 in xmonad: xmonad merge screens when recompile and restart
Status: New Owner: ---- New issue 480 by argu...@gmail.com: xmonad merge screens when recompile and restart http://code.google.com/p/xmonad/issues/detail?id=480 What steps will reproduce the problem? 1. Attach external monitor on VGA port of Thinkpad T410i 2. On terminal: xrandr --output VGA --above LVDS --auto 3. Recompile and restart with mod-q What is the expected output? What do you see instead? xmonad should recompile and restart, xmobar (which is on top of VGA) should restart looking good. xmonad does recompile but when restart it merges everything on LVDS, like if my second screen were also LVDS and seems to treat my external monitor like an extension of LVDS. I just can move windows to VGA by moving the floating window. What version of the product are you using? On what operating system? xmonad 0.9.2 on Archlinux x86_64 Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". No output when "xmonad --recompile" Please provide any additional information below. It doesn't seem to happen when I use "xrandr --output VGA --right-of LVDS --auto" Attachments: xmonad.hs 14.0 KB
Updates: Status: Fixed Comment #1 on issue 480 by vogt.a...@gmail.com: xmonad merge screens when recompile and restart http://code.google.com/p/xmonad/issues/detail?id=480 Please try with 0.10. I'll reproduce Tomas' explanation here (note the patch isn't included in 0.9.2): Thu Nov 19 09:50:43 EST 2009 Tomas Janousek * X.H.ManageDocks: ignore struts that cover an entire screen on that screen Imagine a screen layout like this: 11111111 11111111 11111111 222222 <--- xmobar here 222222 222222 When placing xmobar as indicated, the partial strut property indicates that an entire height of screen 1 is covered by the strut, as well as a few lines at the top of screen 2. The original code would create a screen rectangle of negative height and wreak havoc. This patch causes such strut to be ignored on the screen it covers entirely, resulting in the desired behaviour of a small strut at the top of screen 2. Please note that this semantics of _NET_WM_STRUT and _NET_WM_STRUT_PARTIAL is different to what is in wm-spec. The "correct" thing to do would be to discard the covered portion of screen 1 leaving two narrow areas at the sides, but this new behaviour is probably more desirable in many cases, at least for xmonad/xmobar users. The correct solution of having separate _NET_WM_STRUT_PARTIAL for each Xinerama screen was mentioned in wm-spec maillist in 2007, but has never really been proposed, discussed and included in wm-spec. Hence this "hack".
participants (1)
-
codesite-noreply＠google.com