Terence Devlin wrote:
Whenever I used the iPhoto Reveal in Finder feature, it was only so I could easily and instantly drag the file's icon to another app. Perhaps to Photoshop, or Quicktime 7 or some other application
So, you never knew how to use iPhoto either, particularly the External Editor feature.
Well I was aware of the external editor feature, however, I preferred the flexibility of dragging the icon to the application of my choice. It was far more flexible (external editor was fixed to only one application choice). And what makes you think I didn't know how to use it? I was using a feature of the application "Reveal in Finder". If it wasn't meant to be used, why would Apple have it there in the menu?
Ever since the Mac was conceived, dragging an icon to an app icon has been a fundamental feature. Now in Photos, it lets you drag a photo icon to an app icon, it acts like it is going to open, but doesn't. That is just un-Mac like. I have been using and developing for Macintoshes professionally for over 20 years so I think I have a feel for drag and drop.
If I ever manipulated the image, I just saved as to a file in my home directory.
So, you had a photo manager that you didn't use? And duplicates all over the place?
Ummm no - the photo manager part worked just fine for me. It allowed me to import all my photos in one place, create collections, view by dates and events, search, etc. etc.
And no I didn't have duplicates all over the place either. Most often I would just *view* the image in an external application. In the rare event that I made changes, it was likely saved as a new file format that would be likely be incompatible with iPhoto (eg Photoshop document perhaps with layers etc) and was not an identical duplicate at that point.
Use a Referenced Library (tho' you can't use the iCloud Library if you do this). Then that command works like you want it to.
Or: File -> Export does exactly the same job...
File -> Export does not do the same exact job. For one it creates a duplicate, and most the time I just want to *view* the image in a different application. Why is that so wrong? And for two, it is far more tedious and time consuming compared to just revealing the file.
There was all this talk in this thread that it can't be done because of data corruption. That is just hogwash. Again - the originals permissions could be set to read-only, then it would make people like me happy. (apparently I am not the only one out there that did it all wrong according to you and would very much like the feature back).