Path: utzoo!news-server.csri.toronto.edu!rutgers!gatech!ncar!elroy.jpl.nasa.gov!sdd.hp.com!think.com!paperboy!osf.org!dbrooks
From: dbrooks@osf.org (David Brooks)
Newsgroups: comp.windows.x
Subject: Re: help wanted -- Motif Root Menu
Message-ID: <19962@paperboy.OSF.ORG>
Date: 13 Mar 91 21:30:04 GMT
References: <9103112209.AA26861@pyr.csuhayward.edu>
Sender: news@OSF.ORG
Organization: Open Software Foundation
Lines: 38

wang@pyr.csuhayward.EDU (Hong Wang) writes:
|> 
|> I'm using mwm on X11 R3 running on Sun 3 workstations, which are running
|> Sun OS 4.1. I've had my own customized startup file .mwmrc, resource 
|> file .Xdefaults in my home directory. Root menu and window menu are defined 
|> in .mwmrc. The mwm is brought up by xinit command with .xinitrc file.
|> 
|> When mwm is running, I can pop up the window menu on xterm windows.
|> Contrastingly, I can't get the root menu on root window. Another problem
|> is that the customized window menu doesn't come up. Instead, the window
|> menu defined in the systemwide startup file system.mwmrc keeps coming
|> up. It seems that .mwmrc does not have any effects when mwm is come up.

First, mwm has to know about your .mwmrc, so make sure the resource
Mwm*configFile is pointing at the right filename.  Use "*", not ".".

Next, the Mwm resources *buttonBindings and *keyBindings should have some
string value.  These strings should map to button and key tables in the
.mwmrc.

There should be an entry in these buttonBindings something like:

	<Btn1Down>	root		f.menu	RootMenu

Finally, the menu RootMenu should also be defined in your .mwmrc.

|> When mwm is coming up, there's an error message showing on the console
|> window, saying "mwm: Invalid accelerator specification on line 7 of
|> specification string". I don't know if not getting root menu has some
|> thing to do with this error or not.

Sun 3 which doesn't have a F10 key, or whose server doesn't call it F10,
right?  Make sure your KeyBindings, and the accelerators on various menus,
don't mention F10 (the default does, unfortunately).
-- 
David Brooks				dbrooks@osf.org
Systems Engineering, OSF		uunet!osf.org!dbrooks
"It's not easy, but it is simple."