Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!njin!drew!drunivac!tlimonce
From: tlimonce@drunivac.uucp
Newsgroups: comp.sys.amiga.tech
Subject: Re: Determining disk devices
Message-ID: <28777.25a63df7@drunivac.uucp>
Date: 6 Jan 90 18:50:31 GMT
References: <2924@dogie.macc.wisc.edu>
Lines: 32

In article <2924@dogie.macc.wisc.edu>, gilmore@vms.macc.wisc.edu (Neil Gilmore) writes:
> A good idea, but there must be a way to access floppy volumes not 
> currently known by the system. The drive buttons are quite useful for 
> floppys, less so for hard disks and networks, which tend to be always 
> mounted and have potenrially several volume names per physical device.

Whenever you get a DISKCHANGE through the input.device food-chain you 
could re-scan the system list.  Then your list would be acurate (valid 
selections only) and user-proof (can't select something that shouldn't
be selected).

One school of thought on UI's is that the user should only be able to 
select options that work(*1).  Of course, with the DISKCHANGE message, a 
dynamic display is possible.  If the user really, really wants to 
use a device that wouldn't be on the list (*2) he/she can use the 
keybaord and enter it into the string gadget.

I hope this feature is in the 1.4 filerequester.

-Tom

(*1) -- For example, in pull-down menus the hazy options can't be selected.
(*2) -- For example, the common Usenet complain about GUI's that "I know what 
        I'm doing better than the @*#&$^ computer!"

---
Tom Limoncelli       The computer industry should spend more time in front of
tlimonce@drew.uucp              their computers.  Remember when "Look & Feel"
tlimonce@drew.Bitnet                      was what you tried to do on a date?
limonce@pilot.njin.net

NOTE: REPLY to this message doesn't work (yet), please use tlimonce@drew.uucp