> 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/> > >
