Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site unc.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!mcnc!unc!wfi
From: wfi@unc.UUCP (William F. Ingogly)
Newsgroups: net.cog-eng
Subject: Re: mouse cursors and default menu selections
Message-ID: <29@unc.UUCP>
Date: Sat, 9-Feb-85 15:35:29 EST
Article-I.D.: unc.29
Posted: Sat Feb  9 15:35:29 1985
Date-Received: Mon, 18-Feb-85 06:15:40 EST
References: <420@decwrl.UUCP>, <807@sjuvax.UUCP>
Organization: CS Dept., U. of N. Carolina at Chapel Hill
Lines: 45

> themselves. I often get the impression that too little attention is given
> to the fact that the application user wants to use the program in the least
> brain straining fashion, and in most cases if that means an extra
> centimeter motion of a mouse, big deal.

This is certainly true of the novice user, but the extra movement can
get to be a pain after using the program four hours a day for two
years. With regard to the 'repeat last command' idea, I like Random's
idea from Research Triangle Institute of using an extra menu slot for
the repeat function. But why not have a long, skinny slot that runs
the length of the menu, thus minimizing the hand motion needed to
repeat the last command:

                   ----------------------------
                   |    Command 1      |  R   |
                   |-------------------|  E   |
                   |    Command 2      |  P   |
                   |-------------------|  E   |
                   |    Command 3      |  A   |
                   |-------------------|  T   |
                   |       etc.        |      |

This would allow you to repeat the last command with the same amount
of movement no matter where you were in the menu or how long the menu
was.
> 
> 	With the advent of the popular bitmap display, we have a chance to
> explore thoroughly the implications of user interface design. Apple has
> made a start.  There are things I don't like about it, but we have a chance
> to explore what is good, what we would prefer, and what is *EASY TO USE*.
> Where ease of use does not conflict with flexibility and does not seriously
> infringe on user convenience, I believe it should be actively sought. Is
> having to move the mouse that extra inch really so painful in this light?
> 
> 	Comments are welcome.  I am thinking of doing a thesis on this
> topic and would like to hear alternate views. I would like to see the day
> when the programmer/user interface becomes satisfactory to both. That takes
> compr0mise, but I think that the bitmapped display with mouse/trackball
> has potential.
> 
> 	As usual, my opinions only.
> 
> Jon Shapiro
> Haverford College
>