From owner-freebsd-hackers  Thu Jun  1 11:49:16 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id LAA03107
          for hackers-outgoing; Thu, 1 Jun 1995 11:49:16 -0700
Received: from cs.weber.edu (cs.weber.edu [137.190.16.16])
          by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA03101
          for <hackers@FreeBSD.ORG>; Thu, 1 Jun 1995 11:49:15 -0700
Received: by cs.weber.edu (4.1/SMI-4.1.1)
	id AA03152; Thu, 1 Jun 95 12:40:30 MDT
From: terry@cs.weber.edu (Terry Lambert)
Message-Id: <9506011840.AA03152@cs.weber.edu>
Subject: Re: [On the new Install]
To: peter@bonkers.taronga.com (Peter da Silva)
Date: Thu, 1 Jun 95 12:40:29 MDT
Cc: jkh@freefall.cdrom.com, julian@ref.tfs.com, hackers@FreeBSD.ORG
In-Reply-To: <199506010013.TAA21403@bonkers.taronga.com> from "Peter da Silva" at May 31, 95 07:13:46 pm
X-Mailer: ELM [version 2.4dev PL52]
Sender: hackers-owner@FreeBSD.ORG
Precedence: bulk

> Ah-ha!
> 
> It's motif semantics. "Go to next entry" is "Tab" and return is "OK".
> 
> One of the many ways Motif sucks. You either have to live with it and tell
> people not to hit RETURN until the screen is complete, or make RETURN act
> like TAB and use some other key for RETURN.

You are supposed to use 'tab' and hit 'space' when the tab group that
contains only that button is selected.

To avoid the 'return' behaviour, you have to not set a default button
(and this has to be done explicitly, since the first button in the
button list is default).

The 'return' behaviour is also widget-dependent; for instance, if you
have a multi-line text input widget, it will go to the next line in the
widget instead.  So just changing it to a tab is bogus.


Alternately, you could expect users to understand Motif/MS Windows
semantics by virtue of previous exposure.  8-).


					Terry Lambert
					terry@cs.weber.edu
---
Any opinions in this posting are my own and not those of my present
or previous employers.