Path: utzoo!utgpu!watserv1!watmath!att!rutgers!ucsd!ucbvax!osf.org!sjs
From: sjs@osf.org
Newsgroups: comp.windows.x.motif
Subject: Re: Motif Translations
Message-ID: <9009202003.AA08103@gyoza.osf.org.osf.org>
Date: 20 Sep 90 20:03:13 GMT
References: <9009201937.AA01041@turnpike.Eng.Sun.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 54

Dan Heller writes:

> 
> On Sep 19, 11:51pm, Kee Hinckley wrote:
> > >     *translations: #augment\n\
> > > 	<Key>Help:	Help()
> > > 
> > > This is the only way that I can find to make the Help key call a widget's
> > > help callback.  Even if I had specified the translation argument for
> > 
> > Really?  All I did was add a helpCallback and it all just worked.  1.0 and 1.1.
> 
> I tried that on my sun3/60 and it doesn't work.  Motif seems to think my
> Help key doesn't exist.
> Could be my server, I guess.
> 
> --dan
> 

This is definitely a possibility. It has to do with the way the virtual
bindings are set up. The first thing you need to check is if your server's
vendor string matches the one that Motif has defined for key bindings.
In case you don't know, this can be done using the command 'xdpyinfo'
For example in 1.1:

		/*"X11/NeWS - Sun Microsystems Inc."
 		* OpenWindows 1.0.1 Server for a Sun-4
 		* with a type 4 keyboard */

 		sunFallbackBindingString
			[ Stuff deleted ]

		osfHelp         :               <Key>Help       \n\

		The vendor string is "X11/NeWS - Sun Microsystems Inc."


In this case, the Help key would work normally. However, if your vendor
string doesn't match, you get the default bindings. (Help is the F1 key)
In Motif 1.0, there weren't as many defines for various vendors, so if
you're not on an HP or DEC machine, you are likely to have default
bindings. (There is a good possibility that you would have defaults anyway).

In addition, if you use mwm, you can set up key bindings in your .motifbind
file. This would allow you to specify osfHelp to really be the Help key.
Thie can also be done by setting defaultVirtualBindings in your .Xdefaults
file.

Lastly, your server has to actually know what the heck the key code is for
the key you define. (ie. a Help key has to actually exist.)

Simple huh?   ;-)

Hope this helps....