Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!agate!ucbvax!rtl.enet.dec.com!treggiari
From: treggiari@rtl.enet.dec.com (30-Nov-1990 1456)
Newsgroups: comp.windows.x.motif
Subject: Re: translation problems
Message-ID: <9012010143.AA01942@decpa.pa.dec.com>
Date: 1 Dec 90 01:43:50 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 20

>	My widget is declared as XmDrawingArea
>	widget and it is a child of XmMainWindow widget.
>	In the MrmNcreateCallback for my XmDrawingArea widget I call
>	XtAppAddActions and after XtRealizeWidget(toplevel)
>	for the whole MRM Hierarchy I call XtOverrideTranslations using my own 
>	Translation Table for the XmDrawingArea widget. I also tried to use
>	XtSetValues for XtNtranslations resource specifying my Translation 
>	Table. In either case I can not get the proper behavior. It seems
>	that some of the key translations are accepted while others are 
>	not.

Is your problem Motif's "Virtual Bindings"?  If you don't know about them,
see the reference manual entry for "VirtualBindings".  Essentially, Motif
installs a key translator which maps some real keysyms into osf keysyms.
This key translator is called by the translation manager, so the real
keysyms will never match in a translation entry, but the osf keysyms
will.  For example a "<Key>Right:" will never match, but a "<Key>osfRight:"
will.

Leo