On Tue, Nov 1, 2011 at 3:40 PM, Tim Lawson <[email protected]> wrote: > Nooooo!! Please keep the Finder way of always copying because although I > understand the frustration of some, I think the majority will likely be > confused if you were to make such a change and then you'd be fielding a load > of questions along the lines of"I didn't mean to move my file... where's it > gone?"
But when you select the "move" action, wouldn't you expect that the file...well...moved? But I guess it's all about what people are used to. > Of course, if copying to a different volume using Finder, you can always > hold the option key down to force a move. Could QS be equipped with a > similar way of adding a modifier to achieve this? That'd be cool :-) well, there is the ⌘-return to run an alternative action. "Really move to..." could be the alternative action for "Move to...". > On 1 Nov 2011, at 14:24, Patrick Robertson wrote: > >> So, change [QSFinderProxy moveFiles:toFolder:shouldCopy:] to use the > cocoa method instead of applescript, it should be fine. > Not forgetting to add the 'copy' sound back in ;) > Personally, I prefer the finder method of always copying. But of course we > should change this if the majority of users would prefer it this way :) > > On 1 November 2011 13:31, Henning Jungkurth <[email protected]> > wrote: >> >> > I wonder if there’s a Cocoa way to force a literal move. If not, maybe >> > we >> > should rename the action to “Drag to…” or something. :) >> >> From what I read in the documentation of [NSFileManager >> moveItemAtPath:toPath:error:] >> >> (http://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Classes/NSFileManager_Class/Reference/Reference.html#//apple_ref/occ/instm/NSFileManager/moveItemAtPath:toPath:error:) >> it does a literal move by default: >> If the source and destination of the move operation are not on the >> same volume, this method copies the item first and then removes it >> from its current location. >> >> But QS uses applescript instead, which does the copying instead of >> moving. See here: >> >> https://github.com/quicksilver/Quicksilver/blob/master/Quicksilver/PlugIns-Main/Finder/QSFinderProxy.m#L51 >> >> So, change [QSFinderProxy moveFiles:toFolder:shouldCopy:] to use the >> cocoa method instead of applescript, it should be fine. >> >> >> On Tue, Nov 1, 2011 at 2:06 PM, Rob McBroom <[email protected]> >> wrote: >> > On Nov 1, 2011, at 3:44 AM, Patrick Robertson wrote: >> > >> > This is the correct behaviour, and it reflects what the Finder would do. >> > When copying/moving across a network Finder always choses to Copy, I >> > guess >> > for safety reasons (if your network became disconnected or something) >> > >> > The copy action in Quicksilver always copies. The move action simulates >> > dragging the file in Finder (not necessarily moving or copying). On the >> > same >> > disk, dragging will move. On different disk, dragging will copy. >> > I don’t think it’s a safety thing, because the source file isn’t removed >> > until the “move” finishes. You can move across disks by holding ⌘ while >> > dragging. The reason Quicksilver copies is that there’s no way to supply >> > this modifier. >> > I wonder if there’s a Cocoa way to force a literal move. If not, maybe >> > we >> > should rename the action to “Drag to…” or something. :) >> > -- >> > Rob McBroom >> > <http://www.skurfer.com/> >> > >> > > > >
