Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!dimacs.rutgers.edu!seismo!seismo.CSS.GOV!bonnett
From: bonnett@seismo.CSS.GOV (H. David Bonnett)
Newsgroups: comp.windows.x.motif
Subject: Re: What is the purpose of translation
Message-ID: <49315@seismo.CSS.GOV>
Date: 9 Jan 91 14:26:43 GMT
References: <1149@tredysvr.Tredydev.Unisys.COM> <910108203640.281@alphalpha> <1991Jan8.200305@wsl.dec.com>
Sender: usenet@seismo.CSS.GOV
Reply-To: bonnett@seismo.CSS.GOV
Distribution: inet
Organization: Center for Seismic Studies, Arlington, VA
Lines: 17

In article <1991Jan8.200305@wsl.dec.com>, klee@wsl.dec.com (Ken Lee) writes:
|> In article <910108203640.281@alphalpha>, nazgul@alfalfa.com (Kee Hinckley) writes:
|> |> From what I've seen in previous postings, overriding a translation
|> |> (other than in the code, after the widget is created) will
|> |> cause no other translations to ever be added, due to Motif
|> |> quirks. 
|> 
|> Can you give an example of this?  Changing translations through my
|> .Xdefaults works fine for me.

Ken,
 Try using a .motifbind file and add a binding for something other than
F1 (osfHelp). Restart mwm and see if the context sensitive help works for
you.  I lost this binding until I added it into the file.

-dave bonnett;Center for Seismic Studies, Arlington, VA
      bonnett@seismo.CSS.GOV-