Issue 370 in xmonad: Xinerama, CycleWS & Empt workspaces

Status: New Owner: ---- New issue 370 by seansorrell: Xinerama, CycleWS & Empt workspaces http://code.google.com/p/xmonad/issues/detail?id=370 What steps will reproduce the problem? 1. On a Xinerama setup, pull up one workspace with a window, and one without 2. From the workspace with the window, use a keybinding to call XMonad.Actions.CycleWS nextScreen (or prevScreen) What is the expected output? What do you see instead? The cursor _should_ jump reliably to the screen without the window, but it only works about 3 times out of 10. Suggestion: move the cursor over a few extra pixels to ensure that it really is on the correct screen What version of the product are you using? On what operating system? xmonad 0.9 on Archlinux 64-bit nVidia 9800GT Attachments: xmonad.hs 5.7 KB xorg.conf 1.3 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

Comment #1 on issue 370 by seansorrell: Xinerama, CycleWS & Empt workspaces http://code.google.com/p/xmonad/issues/detail?id=370 Close this one please, it was nothing more than user error. For completeness, I'm attaching a (very small) patch for my supplied config. Attachments: cursor-focus.patch 116 bytes -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

Updates: Status: Invalid Comment #2 on issue 370 by byorgey: Xinerama, CycleWS & Empt workspaces http://code.google.com/p/xmonad/issues/detail?id=370 OK, closing. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
participants (1)
-
codesite-noreply@google.com