Page 1 of 1

Copy To / Move To... Dangers and Problems

Posted: Tue May 14, 2013 10:06 am
by m.Th.
Some problems which are shared between "Copy To" and "Move To" dialogs:
  • If the path isn't ended with a "\" then it is interpreted as a file. This is very dangerous. I don't want to accidentaly rename my serial numbered photos to "reception". When I press Alt+M (Move To...) I want to move all my selected RAW files to C:\Photos\Wedding Inbox\Reception" and not to move the 1st one to the "C:\Photos\Wedding Inbox" and silently rename it "reception", cutting, of course, the .CR2 extension. If doesn't exists already, please add at the end of the path a path delimiter ("\" on Windows) and treat all the strings as paths.
  • Unfortunately the folder must exist. This is very bad. A much more streamlined experience would be if the engine will check for the folder's existence and if doesn't exist, ask "The folder C:\temp\foo doesn't exist. Create?"
  • If the path is relative then it is assumed that it is appended on the executable's (xnview.exe) home folder. This is very confusing. I rather expect that when I type in the destination box "Reception", this will be appended to the current path in the Browser (eg. C:\Photos\Wedding Inbox\ ) and not to the xnview.exe's path (c:\Program Files\XnViewMP\ on my PC). Who wants to Copy To... / Move To... image files to the XnView's folder?
IMHO all the above are rather easy to fix (ok, perhaps the last one needs some parsing) allowing us to organize better our collections.

As an aside, yes, I'm waiting too for the drag & drop support in the folders pane.