Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!kth!draken!tut!santra!kampi.hut.fi!jmunkki
From: jmunkki@kampi.hut.fi (Juri Munkki)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Locking the "chooser" user name?
Message-ID: <23016@santra.UUCP>
Date: 21 Jun 89 11:40:34 GMT
References: <1889@dogie.macc.wisc.edu> <22951@santra.UUCP> <7697@hoptoad.uucp> <22959@santra.UUCP> <7720@hoptoad.uucp>
Sender: news@santra.UUCP
Reply-To: jmunkki@kampi.hut.fi (Juri Munkki)
Organization: Helsinki University of Technology, Finland
Lines: 25


In article <7720@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
<In <22959@santra.UUCP> jmunkki@kampi.hut.fi.hut.fi (Juri Munkki) writes
<>I knew there would be a copy in RAM and the good thing is that the
<>user thinks the name is changed when it's not actually written to
<>disk.
<
<The good thing?  In what way is a misleading feature that only partially
<does the job a good thing?
<
<The misleading part is especially bad.  Just we we need is for the users
<of a Macintosh to be less certain that it will behave predictably and
<obviously, so they will rveert to the "I'm afraid to type 'help' because
<it might erase all my files" so common on other machines.  If there is a
<good solution, it is one that doesn't confuse the user.

The original posting wanted an INIT that would "fix" the choosername
every time the Mac is restarted. Probably the best solution is to set
the protected bit _and_ change the chooser edit text item into a static
text item.

_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
|     Juri Munkki jmunkki@hut.fi  jmunkki@fingate.bitnet        I Want   Ne   |
|     Helsinki University of Technology Computing Centre        My Own   XT   |
^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^