It's really the only reasonable solution - we need the fingertip-bits,
too.
If we can't make the menus key-controlled, I'll make it a preference or
reasonable mixture of the too. 
The code attached is a rough start - it makes MenuMorph handle keyboard
input (up down enter), but for some reason only works when the mouse is
not over the menu (note that the menu will retain keyboard focus so long
as you don't make another morph demand it). This makes it a start, but
useless for our purposes... 
Clues or ideas welcome, I'm down to considering redefining menus in
terms of lists...

"Lex Spoon" <lex at cc.gatech.edu> wrote:
> How about:
> 	1. mouse click gives you the menu
> 	2. keypress gives you the best choice
> Also, if menus ever start responding to keypresses, then menus popping
> up won't be so annoying--you could just hit alt-c followed by enter,
> which is pretty speedy.  (And if you need faster than that, then your
> average time per email is *really* low, and you have another problem!)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MenuMorph.cs.gz
Type: application/octet-stream
Size: 748 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20000708/28d793ab/MenuMorph.cs.obj
-------------- next part --------------