home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.mac.programmer
- Path: sparky!uunet!sun-barr!ames!ads.com!killer!pokey.verity.com!anders
- From: Anders Wallgren <anders@verity.com>
- Subject: Re: Human Interface questions, specific functionality
- Organization: Verity, Inc., Mountain View, CA, USA
- Date: Thu, 27 Aug 92 23:09:32 GMT
- Message-ID: <1992Aug27.230932.11741@verity.com>
- X-Xxmessage-Id: <A6C2AF44F101C897@pokey.verity.com>
- X-Useragent: Nuntius v1.1.1d9
- References: <1992Aug27.175328.1@tesla.njit.edu>
- Sender: usenet@verity.com (USENET News)
- X-Xxdate: Thu, 27 Aug 92 00:11:48 GMT
- Lines: 29
-
- In article <1992Aug27.175328.1@tesla.njit.edu> Elliotte Rusty
- Harold, erh0362@tesla.njit.edu writes:
- > 2. A user opens a file on a locked disk and makes changes to it.
-
- > (Alternately the user locks the disk while the file is open.)
- When
- > the user attempts to save should I
- >
- > a) Simply post an error message saying the disk is locked?
- > b) Check that the disk is locked before every save (If so
- how?)
- > and if it is do a Save As instead?
- > c) Check that the disk is locked before every save
- > and eject the disk and post a dialog asking the user to unlock
- > and reinsert it?
-
- If the user opens a file that is locked or that is on a locked
- volume, you should probably warn them that any changes they make
- can't be saved to that file. You might still enable Save and treat
- that command like Save As (or treat it like they're saving a new
- document).
-
- If the disk becomes locked after the user has already opened the
- file for writing, you should probably give them whatever error
- message makes most sense, and perhaps prompt them to do a Save As
- (verbally, not by putting the dialog up).
-
- You probably shouldn't do choice c), since the user should control
- when the disk is ejected.
-