Does SetWMName hack work when you are starting the MATLAB on local machine?

Are you pressing the keys which set the WM name before the start the MATLAB? Once the JVM inside which the MATLAB is running has been started, changing the name of the WM does not affect this particular JVM (it only checks which WM is used once on startup).

If this still does not work, can you please try adding AWT_TOOLKIT=MToolkit line to the ~/.ssh/environment and make sure that it gets into the environment of the remote machine at startup of your ssh session.

Ivan

On 10/12/07, Christian Thiemann <mail@christian-thiemann.de> wrote:
Hi Ivan,

I still have some trouble with MATLAB.  As I reported earlier, the
AWT_TOOLKIT=MToolkit hack worked for me, but - as I discovered later -
only if I run MATLAB from the local machine.  If I want to spawn it
remotely on one of our computing machines (via ssh -X) nothing will show
up at all.

Today I tried it with your SetWMName extension (for which I needed to
change from 0.3 to darcs), but it doesn't work :-(

As in the module docs, I use setWMName "LG3D" (I tried to put it in my
logHook first, and also triggering manually via a keypress), but the
error is still the same (just blank grey screen with menus popping up
properly but no widgets at all).

I am thankful for any suggestions.

Best regards,
   Christian


Ivan Tarasov wrote:
> 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 <mailto: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 <http://xmonad.org/faq.html > page please?
>
>     -- Don
>     _______________________________________________
>     Xmonad mailing list
>     Xmonad@haskell.org <mailto: Xmonad@haskell.org>
>     http://www.haskell.org/mailman/listinfo/xmonad
>
>
_______________________________________________
Xmonad mailing list
Xmonad@haskell.org
http://www.haskell.org/mailman/listinfo/xmonad