bonnett@seismo.CSS.GOV (H. David Bonnett) (01/03/91)
I have tried a variety of things and RTFM'd until I wanna FTFM's (guess..)
without success, so I turn to the gods (or whoever can help)
I have a 1.1 app that has a bunch of XmTextFields, some by themselves in
popups, and some laid out in forms. For the solitary fields I want the
Return key to do call the Activate callback. To do this I have placed this
in my .motifbind file: osfActivate : <Key>Return
This gives the desired response.
Now for the problem: -> In the cases where there are more than one
TextField on the form, I want the Return key to act like a tab and
go the the next tabgroup. So far I have tried a second line in the
.motifbind file : osfActivate : <Key>Return
osfNextField : <Key>Return
but I didn't expect that to fly (no warnings or removal of the first
action though ).
Next I tried to add to the translations for the widget with
XtOverrideTranslations(text_field_widg,
XtParseTranslationTable
("<Key>Return: next-tab-group()"));
I have also tried Augment in place of Override.
Now the results of this vary by which action I attempt to use
with the key. If I use next-tab-group I get nothing; no warnings,
no traversal. If I use process-tab, I get a warning from the Trans Man:
Warning: Actions not found: process-tab
Both of these are listed in the XmText actions list for 1.1 and both
show up in the 1.1 source for TextIn.c in the default actions table:
{"process-tab", (XtActionProc)ProcessTab},
{"next-tab-group", (XtActionProc)TraverseNextTabGroup},
I would greatly appreciate any pointers or dogma on how to handle this.
The implements of destruction are Motif 1.1 on Sun 4.1.1 on a Sparc.
-dave bonnett; Center for Seismic Studies, Arlington, VA
bonnett@seismo.CSS.GOV-