Path: utzoo!attcan!uunet!microsoft!michaelt
From: michaelt@microsoft.UUCP (Michael THURLKILL)
Newsgroups: comp.windows.ms
Subject: Re: Sad
Message-ID: <55208@microsoft.UUCP>
Date: 13 Jun 90 18:09:46 GMT
References: <9963@sbcs.sunysb.edu> <3130005@hplsla.HP.COM>
Reply-To: michaelt@microsoft.UUCP (Michael THURLKILL)
Organization: Microsoft Corp., Redmond WA
Lines: 28

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.  (And I can't figure out how to make
>it do a "move", that is copy from first directory on first drive to second
>directory on second drive and then delete original.)  I would expect that
>move is move (irregardless if it is same drive or not) and copy and copy
>(irregardless if it is same drive or not).

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. Therefore the FileManager tries to be smart.
If you want explicit control:
Ctrl-Drag copies
Alt-Drag  moves 
This is true whether you are going local to local, remote to local,
local to remote, or remote to remote.

Mike Thurlkill

Disclaimer: These are my opinions. They should in no way be
miscontrued as being correct or in any way related to my employer.