I'm the author of SetWMName and I can summarise the issue, however I already tried to do this in the comment in the beginning of the SetWMName.hs. If it is not enough, please advice on how to improve the summary. If it is possible, you should use the SetWMName instead of setting AWT_TOOLKIT=MToolkit, because MToolkit (Motif, actually) is an old engine for AWT and it doesn't support all the features needed to make the Java GUI programs work (some programs work, some do not). Setting WM name is quite a dirty hack, but it is the only way to work around the problem till, maybe, JDK7 (and there are no guarantees we'd have anything fixed there). Ivan On 10/2/07, Don Stewart <dons@galois.com> wrote:
mail:
Brandon S. Allbery KF8NH wrote:
On Oct 1, 2007, at 10:04 , Stefan O'Rear wrote:
On Mon, Oct 01, 2007 at 02:28:25PM +0200, Christian Thiemann wrote:
It looks like it's a problem with Xmonad. I fired up an Xnest with
fvwm
and MATLAB works fine there. And Xnest with wmii and MATLAB works as well.
Is the MATLAB gui written in Java? There is a known bug in the Java windowing code which prevents it from working correctly with non-reparenting window managers like xmonad.
Yes, the Matlab GUI is Java.
Another known workaround that often (but not always, for unknown reasons) works is
export AWT_TOOLKIT=MToolkit
before starting Java programs.
Ok, great. That worked for me. Thanks. _______________________________________________
could someone summarise this issue generically, with the fix details, for the xmonad.org/faq.html page please?
-- Don _______________________________________________ Xmonad mailing list Xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad