From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from ben.uknet.ac.uk ([192.91.199.254]) by hawkwind.utcs.toronto.edu with SMTP id <2764>; Thu, 1 Jul 1993 16:33:01 -0400
Received: from a.gec-epl.co.uk by ben.uknet.ac.uk via PSS with NIFTP (PP) 
          id <sg.11954-0@ben.uknet.ac.uk>; Thu, 1 Jul 1993 21:32:29 +0100
Received: by zombie.gec-epl.co.uk (5.0/SMI-SVR4) id AA00635;
          Thu, 1 Jul 93 21:33:35 BST
Date:	Thu, 1 Jul 1993 16:33:35 -0400
From:	steve@gec-epl.co.uk (Steve_Kilbane)
Message-Id: <9307012033.AA00635@zombie.gec-epl.co.uk>
To:	sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: scrolling menus
X-Sun-Charset: US-ASCII

the original version of sam had menus that scrolled when the file menu got
too long (what determined when it was "too long", i don't know) - see the
V10 Research UNIX Programmer's Manual, Volume II. About p399, if i remember
correctly:-).

anyway, when i had the chance to see it, it didn't look too pleasant to use,
because there was too much unpredictability in how the menu scrolled. i
don't know, maybe it was just me. but i don't like the idea of cascading
menus either (too much holding down of the button again). i think the simplest
method would be to just have a "more files" option, just above "~~sam~~",
which cycles through which set of files appear in the menu. it's not
complicated to use, and probably not complicated to implement either (i
haven't looked at the menu code for a while, but it wasn't that difficult).
the main problem is that getting to your file could take n selections from
the menu, and you know how much rob hates unnecessary user interaction... :-)

steve