Path: utzoo!attcan!uunet!snorkelwacker!usc!cs.utexas.edu!rutgers!rochester!newkodak!isctsse!pajerek
From: pajerek@usenet@kadsma (Don Pajerek)
Newsgroups: comp.windows.ms
Subject: Re: Sad
Message-ID: <1990Jun13.205440.12665@usenet@kadsma>
Date: 13 Jun 90 20:54:40 GMT
References: <9963@sbcs.sunysb.edu> <3130005@hplsla.HP.COM> <55208@microsoft.UUCP>
Reply-To: pajerek@kadsma.UUCP (Don Pajerek)
Organization: Eastman Kodak Telecommunication Services, Rochester, N.Y. 14650
Lines: 31

In article <55208@microsoft.UUCP> michaelt@microsoft.UUCP (Michael THURLKILL) writes:
>In article <3130005@hplsla.HP.COM> davidr@hplsla.HP.COM (David M. Reed) writes:
>>In line with the "little things" that irritate me.  A simple one is the 
>>copy/move under File Manager.  It is inconsistent.  If I select a file in
>>one directory and tell it to copy to another directory, if the two directories
>>are on the same drive it does a move.  (You have to use the CTRL key in
>>combination with the mouse to mean "copy").  But if the two directories are
>>on separate drives, then it does a copy.
>
>I remember hearing alot of discussion about this feature during
>development. You may not necessarily agree with this, but it was
>decided, from user tests, that when a person drags a file from one
>place to another on the same drive, they usually want it moved,
>and when they drag a file from one drive to another, they usually
>want it copied.
>
>Mike Thurlkill
>


Somebody correct me if I'm wrong, but isn't this also the way the
Macintosh 'Finder' works? If you drag from one folder to another on
the same drive, the file is moved. If you drag to a folder on another
drive, the file is copied.

Is this perhaps where the expectations came from in the tests run
by M'soft? Some of the subjects may have been exposed to the Mac...



Don Pajerek