Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!pt.cs.cmu.edu!henry.ece.cmu.edu!hairston From: hairston@henry.ece.cmu.edu (David Hairston) Newsgroups: comp.sys.mac.system Subject: Re: Inappropriate dialog under 7.0... Message-ID: <13360@pt.cs.cmu.edu> Date: 10 Jun 91 15:56:40 GMT References: Organization: Gaia II Lines: 35 [rdd@cactus.org (Robert Dorsett) writes:] [] The setup: copying files to a disk which already has identical files on it. [] The resulting dialog: [] "Some items in this location have the same names as items you're [] moving. Do you want to replace them with the onces you're moving?" [] Could cause some alarm, especially if the user takes it at face value [] (i.e., moving = copy + delete). [norton@extro.ucc.su.OZ.AU (Norton Chia) replies:] [] At face value, replacing with the on(c)es you're moving means exactly [] that -> I'm going to wipe out (replace) the stuff with the ones I'm [] copying across (moving). So what's the alarm? [kiran@copper.ucs.indiana.edu (Kiran Wagle) writes:] [] But you're not moving them. You're copying them. If you were [] moving a file, you'd still only have one of it. But if you copy it to [] another disk, you have two of it. [norton@extro.ucc.su.OZ.AU (Norton Chia) writes:] [] Well, I don't know of any "move" command in the Finder. I'm suggesting it's [] either the metaphor that's got to change, or your perception of "moving" [] ... perhaps the wording could change for those who would confuse moving and copying but it should be noted that on the Mac (Finder) copying files has never implied moving. the confusion is introduced by ... let's say, outsiders ... and yes, the default should be to protect the files involved, since you could use the default (repeatedly) and if it wasn't what you wanted then you could back and do it right the next time. this is, of course, less convenient than the current method. -dave- hairston@henry.ece.cmu.edu