| 52 | | In non-reparenting window managers (i.e. xmonad, awesome) you are likely to stumble across [http://article.gmane.org/gmane.comp.lang.haskell.xmonad/1790 this old bug] that's still in Java's AWT code. The above mentioned AWT_TOOLKIT=MToolkit trick works around this bug if you're using Sun's (non-free) Java 1.5, but otherwise you'll want to fool java into thinking that your window manager is LG3D, for which they've implemented some sort of fix. |
| 53 | | |
| 54 | | For '''xmonad''', you can get it to lie for you [http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-SetWMName.html thus], as shown [http://github.com/htr/dotfiles/blob/352231b953126cafc234346b9e9a4fe88d500565/xmonad/xmonad.hs here]. |
| | 52 | AWT before JDK7 [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6574362 doesn't play well] with non-reparenting window managers (i.e. xmonad, awesome, dwm, ratpoison, Ion3, ...), resulting in the main window not being displayed properly on startup. The Awesome Wiki has [http://awesome.naquadah.org/wiki/Problems_with_Java workarounds] for this problem. There is also an [http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-SetWMName.html xmonad specific] way of doing the wmname thing. |
