Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!peregrine!sceard!ncr-sd!se-sd!manny
From: manny@se-sd.SanDiego.NCR.COM (Manny Bagnas)
Newsgroups: comp.windows.x.motif
Subject: Re: Using the return key for traversal?
Keywords: Help, Traversal
Message-ID: <4403@se-sd.SanDiego.NCR.COM>
Date: 13 Feb 91 15:54:06 GMT
References: <1991Feb12.113638.5936@siesoft.co.uk>
Reply-To: manny@se-sd.SanDiego.NCR.COM (Manny Bagnas)
Distribution: comp
Organization: NCR Corp., Systems Engineering - San Diego
Lines: 27

In article <1991Feb12.113638.5936@siesoft.co.uk> stuart@siesoft.co.uk (Stuart Hood) writes:

>I have a main window with two child, text widgets.  The main window
>is a tab group so that the user may use the cursor up and down keys
>to navigate between the two text objects.
>
>I would like somehow to have the return key behave like the cursor
>down key, i.e. if the user hits return then it navigates to the
>next text object as if they had pressed the cursor down key.

How about this:

Modify translations for the text widget.  This can be done through the
X resource mechanism (i.e. an app-defaults file for your application), or
or modify translations in the source.

A simple app-defaults file would look like this:

Your-App-Class*XmText*translations:	#override <Key>Return:  traverse-next()

If you had other text widgets in your application which require
a different behavior, then you'd need to modify the above resource to use 
the text widget names rather than class.

Works for me...

Manny