When I try to copy over a pre-existing file, the standard Windows confirmation box comes up rather than a FreeCommander box. In XP, this isn't too big a deal, as the default box does about what I'd want. But in Vista it's a PITA because the default box is huge and has the wrong default, and requires several keystrokes to select "Copy".
What I would like is the option of using a FreeCommander confirmation box instead (both for copying/moving to disk and to zip) and the ability to set the default. The only other Windows file manager I have recent experience with, Directory Opus, does have it's own confirmation boxes which do what I'm wanting.
Standardized Copy-File Confirmation Box
It's taken a bit of work, but I'm closer to a resolution. Using Killcopy set up as follows:
FileMovePrg=killcopy.exe |%ActivSelAsFile%|%InactivDir%| -g-m
FileCopyPrg=killcopy.exe |%ActivSelAsFile%|%InactivDir%| -g
And also acting as the drag-and-drop handler, I now can get the Killcopy confirmation consistently rather than the windows one, and can limit it to the cases I care about. It's an improvement, but unfortunately it's still a dollar short... the default is "abort". So both <enter> and <escape> result in aborting. I want <enter> to be copy and <escape> to be abort. Maybe I'll have to write my own.
FileMovePrg=killcopy.exe |%ActivSelAsFile%|%InactivDir%| -g-m
FileCopyPrg=killcopy.exe |%ActivSelAsFile%|%InactivDir%| -g
And also acting as the drag-and-drop handler, I now can get the Killcopy confirmation consistently rather than the windows one, and can limit it to the cases I care about. It's an improvement, but unfortunately it's still a dollar short... the default is "abort". So both <enter> and <escape> result in aborting. I want <enter> to be copy and <escape> to be abort. Maybe I'll have to write my own.
Who is online
Users browsing this forum: No registered users and 48 guests