Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwm.edu!wuarchive!sdd.hp.com!elroy.jpl.nasa.gov!jarthur!uunet!xyvi!mef
From: mef@xyvi.UUCP (Mike Feldman)
Newsgroups: comp.windows.x.motif
Subject: Translation Tables
Message-ID: <252@xyvi.UUCP>
Date: 28 Nov 90 15:08:49 GMT
Organization: Xyvision Inc., Wakefield,MA
Lines: 27



	I have a problem specifying a Translation Table for a Motif 
	widget. The Translation Table gets corrupted or overridden
	and leads to some unexpected functionality of the keyboard 
	keys.

	Here is what I do:
	
	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.

	Should I be using the inputCallback resource in some way or am I
	doing something else wrong ? ( Is there a known Motif bug with
	Translations?)

	We running Motif 1.1 on DECstations w/ Ultrix 4.0 

	Any help is greatly appreciated...