OS X 10.5: The dock - is command click supposed to work like this?
April 27, 2008 @ 15:29
If command clicking an application in your dock, Finder will fire up a new window at the path were the application resides. For most applications, this means that I will get a Finder window with the Applications folder opened, and the clicked application selected. This is a neat function.
What would be equally nice is if you could command click any folder you have in your dock to make Finder open up a new window showing the contents of that folder. But… the problem is that command click behaves exactly the same way when command clicking on folders as it does when clicking on files; it opens up the parent folder, and then makes sure that the current selection is the item I just clicked.
There might be a good reason for this symmetric behaviour, but I cannot seem to understand why it behaves like this. In my eyes, it would be much better if command clicking a folder opened up that very folder, with an empty selection. That would mean that if I command clicked the Downloads folder (yepp, I’m talking about one of the default folders in the dock) Finder would show me my downloaded files. Seems like a logic choice, right?
Until (if ever) Apple fixes this, there’s some additional clicks one has to perform to actually show the contents of the files. And… as you all know; each unnecessary click kills a kitten somewhere on planet earth. Or was it perhaps masturbation that caused this?
Leave a Reply
Featured articles
- RSS feeds - the hidden gems of delicious
(December 28, 2008 – No Comments) - Command of the day: nl
(December 18, 2008 – No Comments) - Ain’t no language high enough
(December 17, 2008 – No Comments) - Google Mail / Safari: Stealing focus when loading is complete is not OK
(December 7, 2008 – 1 Comment)