Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!mips!sgi!shinobu!odin!sgihub!dragon!news
From: mikey@eukanuba.wpd.sgi.com (Mike Yang)
Newsgroups: comp.windows.x.motif
Subject: Re: .mwmrc errors
Message-ID: <1991Feb15.163505.28361@dragon.wpd.sgi.com>
Date: 15 Feb 91 16:35:05 GMT
References: <12342@sybase.sybase.com>
Sender: news@dragon.wpd.sgi.com (CNews Account)
Organization: Silicon Graphics, Inc.
Lines: 29

In article <12342@sybase.sybase.com> mw@pluto.sybase.com (Michael Wertheim) writes:
>I have a Decstation 3100 workstation, and I am trying to get mwm to run on it.
>When I run the mwm that comes with the machine, mwm starts up, but it seems
>that it does not read my .mwmrc file.  Here's the strange thing: when I run mwm
>from a MIPS machine (over the network), the MIPS version of mwm has no problem
>reading my .mwmrc file, and all of my buttons and menus behave as I expected.
>When I run mwm from another Decstation or from a Sparcstation, they also have
>the same problem reading .mwmrc.  No error message is printed, but the buttons
>and menus do not get defined.  Only the MIPS mwm seems to work.

Most likely your Mwm*buttonBindings and/or Mwm*keyBindings resources
are not getting set correctly.  These need to match whatever you use
in your .mwmrc file.

Remember that although running mwm on the MIPS machine and displaying
on your machine will use an xrdb-installed resource property, it will
still use the locally installed app-defaults file.

Therefore, if the MIPS app-defaults file for mwm differs from the ones
on the DEC and Sun machine, that could explain the differences in
behavior.

My suggestion is to explicitly set Mwm*buttonBindings and
Mwm*keyBindings in your .Xdefaults to correspond with your .mwmrc
contents.

-----------------------------------------------------------------------
                 Mike Yang        Silicon Graphics, Inc.
               mikey@sgi.com           415/335-1786