Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the '10.6: Paste a file path directly into a Save dialog' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.6: Paste a file path directly into a Save dialog
Authored by: mantrid on Jul 07, '11 03:58:10PM
Copying a file is copying a file.
Not exactly. When you copy a file in the Finder, you aren't really copying a file. Depending on the type of file, the clipboard contains multiple classes including url (more or less the path), the icon, the file name, etc. What gets pasted depends on the context and is a design choice, and good design choices contribute to intuitiveness and user-friendliness of the GUI as a whole. If you are pasting in a Finder window, sure enough, a copy of the file is created, just as if you had copied the file. Paste into a mail document, you get an attachment. Paste into a plain text file, you get the file name. Paste in the right part of a Get Info window, you paste the icon. Paste into a TextEdit rtf file and if the source file was an image, it follows the url and actually pastes the image! (and if you actually wanted the name rather than the image, Paste and Match Style instead).

So again, when pasting into the NAME field of a Save dialog, why is it more appropriate to paste the path than the name?

[ Reply to This | # ]

10.6: Paste a file path directly into a Save dialog
Authored by: jaydisc on Jul 07, '11 04:14:24PM

I'm aware of the different forms of data stored on the clipboard as well as how the clipboard correctly reacts depending on the context of where you're pasting it.

I'd say that the best possible solution for what clipboard-class to paste would depend on what aspect of the Save dialog has focus. If the destination file's proposed name has focus, I'd agree that just the copied file's name would seem the appropriate context. But if the file/folder hierarchy of the save dialog had focus. I'd then want the path of the copied file to take precedent.

However, in the absence of that differentiation, I'd then place the burden of context on the copied source. Seeing as the user can specifically highlight and copy the text of the filename, whereas there is no ability to highlight and select the path, it seems more flexible (and appropriate) that the path is the default.

[ Reply to This | # ]