April 2008 - xmonad - Haskell.org

Issue 178 in xmonad: UpdatePointer behavior not usable with Tabbed layout
by codesite-noreply＠google.com 15 Apr '08

15 Apr '08

Issue 178: UpdatePointer behavior not usable with Tabbed layout http://code.google.com/p/xmonad/issues/detail?id=178 Comment #2 by laylward: I am having trouble applying this patch. Maybe it is just me, though? darcs failed: Patch bundle failed hash! This probably means that the patch has been corrupted by a mailer. The most likely culprit is CRLF newlines. -- 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

2 1

Issue 178 in xmonad: UpdatePointer behavior not usable with Tabbed layout
by codesite-noreply＠google.com 15 Apr '08

15 Apr '08

Issue 178: UpdatePointer behavior not usable with Tabbed layout http://code.google.com/p/xmonad/issues/detail?id=178 Comment #1 by robr...(a)bobturf.org: The attached patch should fix it Attachments: updatepointer.patch 8.0 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

1 0

Patch: IM layout converted to LayoutModifier
by veselov＠gmail.com 14 Apr '08

14 Apr '08

Hi all! I've attached a patch, which converts XMonad.Layout.IM to layout modifier, so it can be applied to any layout. I found it quite useful when applied to the tabbed layout: this way we can emulate tabs for IM clients, which don't support tabs out of the box (Skype, etc.). P.S. Old 'data IM' is not deleted yet for compatibility with old configs. -- WBR, Ivan N. Veselov aka sphynx

2 2

Issue 179 in xmonad: Tabbed Layout does not scale for >50 windows
by codesite-noreply＠google.com 14 Apr '08

14 Apr '08

Issue 179: Tabbed Layout does not scale for >50 windows http://code.google.com/p/xmonad/issues/detail?id=179 New issue report by clem...(a)endorphin.org: Using Tabbed with a lot of windows makes it quite slow. There seems to be non-linear work that really kills xmonad after exceeding 60 windows in a single Tabbed Layout. I tried with xmonad-contrib-darcs (checkout yesterday) Here is my quite useless profiling http://clemens.endorphin.org/xmonad.prof -- I started with a Tabbed session and starting opening xterms until the whole thing got real slow. It's quite likely to be related to the excess memory chewing (8gb after 37seconds). If anyone has hints how profile xmonad-contrib better please let me know (I got -auto-all on X11 and XMC thanks to dons' recent patch). xmonad 0.5 has scaled a bit better, so I guess this complexity is due to some "recent" change. 0.6 is also ok, but still it seemed a bit slower (sorry for the vague terms, but without profiling it's hard to tell). With 0.7 there is definitely a problem Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- 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

1 0

darcs patch: Allow users to choose whether the tabbar should always...
by ivan.miljenovic＠gmail.com 14 Apr '08

14 Apr '08

Mon Apr 14 15:11:04 EST 2008 Ivan.Miljenovic(a)gmail.com * Allow users to choose whether the tabbar should always be visible. This uses the improved data structures/code layout from my second patch, but taking into account suggestions by droundy and sjanssen uses the duplicated-methods found in my first patch so that configs currently using Tabbed don't break.

3 3

Issue 178 in xmonad: UpdatePointer behavior not usable with Tabbed layout
by codesite-noreply＠google.com 14 Apr '08

14 Apr '08

Issue 178: UpdatePointer behavior not usable with Tabbed layout http://code.google.com/p/xmonad/issues/detail?id=178 New issue report by laylward: What steps will reproduce the problem? 1. Set up UpdatePointer and Tabbed in your config 2. Open mulitple tabs on a workspace 3. Click on one of the tabs 4. UpdatePointer will move the mouse far away What is the expected output? What do you see instead? It would be much better if UpdatePointer would leave the mouse alone if the change was caused by a mouse click. What version of the product are you using? On what operating system? latest darcs on Debian sid Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- 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

1 0

Issue 177 in xmonad: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol
by codesite-noreply＠google.com 14 Apr '08

14 Apr '08

Issue 177: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol http://code.google.com/p/xmonad/issues/detail?id=177 Comment #2 by Ivan.Tarasov: failed fix attempt patch is in the attachment Attachments: issue177.darcs-patch 2.2 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

1 0

Issue 177 in xmonad: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol
by codesite-noreply＠google.com 14 Apr '08

14 Apr '08

Issue 177: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol http://code.google.com/p/xmonad/issues/detail?id=177 Comment #1 by SpencerJanssen: Please attach a patch in 'darcs send' format, this makes it much easier for us to see what has been changed. -- 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

1 0

Re: Patch: IM layout converted to LayoutModifier
by Ivan Veselov 14 Apr '08

14 Apr '08

Yes, it seems I've hurried up with the patch and it doesn't work good with Tabbed yet, only with Grid and other simple layouts. I'm investigating the problem, sorry for the false start. WBR, Ivan N. Veselov aka sphynx

1 0

Issue 177 in xmonad: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol
by codesite-noreply＠google.com 14 Apr '08

14 Apr '08

Issue 177: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol http://code.google.com/p/xmonad/issues/detail?id=177 New issue report by Ivan.Tarasov: What steps will reproduce the problem? 1. run any Java application (use JDK1.6u1 or higher and xmonad with SetWMName extension to overcome the gray rectangle bug). E.g. run Notepad demo from demo/jfc/Stylepad directory in JDK home, like so: java -jar $JDK_LOCATION/demo/jfc/Stylepad/Stylepad.jar 2. After starting the window doesn't get focus (that's a first example of the problem) 3. click inside the window, so it gets focus. If it is a Stylepad application, you'd be able to enter text in the editor window 4. Switch to another window on the same workspace, either using keys, or mouse 5. Switch back 6. Although the frame around the Java app becomes highlighted (meaning xmonad thinks it has the focus), Java app doesn't seem to get the focus (you cannot edit the text or open menus in Stylepad until you click with your mouse into the window) What is the expected output? What do you see instead? Java application should get the focus after switching back to its window from another window. What version of the product are you using? On what operating system? xmonad 0.7 + latest patches from the repository Debian GNU/Linux, 2.6.24-3 Please provide any additional information below. I've done an investigation together with Java AWT engineers and we've found that this is a problem in xmonad, not in Java. The problem is that xmonad ignores the WM_TAKE_FOCUS protocol which is described in the ICCCM (see http://tronche.com/gui/x/icccm/sec-4.html#s-4.1.7) Java sets <Globally Active> model for its Frames/Dialogs, and <No Input> model for its Windows. In both of these cases the WM shouldn't call XSetInputFocus by itself. In the former case it should send the WM_TAKE_FOCUS event to the window (when it decides that the toplevel window should get the focus), in the latter case it shouldn't do anything (Java processes all the clicks by itself). See also the attached C file. You can compile it using the following command: gcc -o native -I/usr/X11R6/include -L/usr/X11R6/lib -lX11 native.c When run, this file file prints the FocusIn/FocusOut events and also it prints WM_TAKE_FOCUS events if they are sent. The correct behaviour of this program in the WM is to print the message "event on frame %i: WM_TAKE_FOCUS" (where %i is the number of frame, 0 or 1 in this program) whenever the focus is set to its window using the WM (either using keys, or mouse). Incorrect behaviour is when it prints only pairs of the "FocusIn"/"FocusOut" messages. I tried reproducing the same problem in IceWM and found that it handles the WM_TAKE_FOCUS protocol correctly (both on this test program and on real applications). I attempted to fix the problem myself but for some reason the fix didn't work. See the attached Operations.hs file which contains the fix attempt starting with the line -------- WM_TAKE_FOCUS fix attempt starts here -------- If you have any questions or need any further clarification from the Java AWT engineers, please contact me at Ivan.Tarasov(a)gmail.com. I consider this problem as "quite serious" (on some abstract seriousness scale), because it ruins the xmonad using experience as well as Java application using experience when they are used together. Attachments: native.c 2.5 KB Operations.hs 22.1 KB Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- 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

1 0