There was a thread on the topic over here:īut it hasn't seemed to have resolved the issue. So basically, the OSX believes a JPG it opens in Preview without any ado to be an App. The item is either locked or damaged, or in a folder you don’t have permission to modify (error code -10823). You can’t change the item “image_name_here.jpg” to always open in the selected application. BUT at the same time, I get an error box, telling me that Once I click 'Open', the image will open in Photoshop. I can then also tick the box 'Always Open With'. I need to click on 'Enable Recommended Apps' and change that to 'All applications'. "Open With." -> "Other" -> double-click the Photoshop CC19 Folder The only way to get them to open via the right-click menu in Finder is to go via I just cannot drag-and-drop them into Photoshop anymore. Double-clicking on the JPGs will open them in Preview without any problem whatsoever. I'm a graphic designer and have a huge archive of photos I need to constantly use. So it only gives me either Preview as the default, or else the Terminal. jpgs (nice ones from professional image platforms and large publishers) to be apps. This is because there is no selection for Photoshop anymore, as the OSX believes the. jpg-Files cannot be opened in Photoshop via right-mouse-click and the drop-down menu "Open With. Bluetooth problems aside, I now noticed that many of my. jpg is an app from an 'unidentified developer' I have only just upgraded from a MacBook Pro 13" Late-2013 to a brand new MacBook Pro 15" (2018). "You can’t change the item to always open in the selected application." OSX thinks. I just had to research a bit to fix a Photostick for my dad. But most know someone who could do this fix for them if they can't do it themselves. Most who use a Photostick are older folks, so they can easily make the mistake of deleting the alias. But since it's hidden, you can't launch it if you delete the alias that is there when it's brand new.īut hopefully now, MacOS users can fix this. Why they couldn't inhibit accidentally deleting the alias that launches the app itself I have no idea. But now you can simply plug in your Photostick, open it, and double click the nice new alias you created, and the MacOS Photostick Application will run as before, and you can actually use it again. Now you can rehide system files with the command below in the Terminal window and pressing enter.ĭefaults write AppleShowAllFiles -boolean false killall FinderĪll fixed! No idea how to make it auto launch when you open the Photostick USB key itself. And while you're at it, right click the alias, select "get info", and click the checkbox by "locked"! Then at least it's a little harder to accidentally delete it. Copy this alias file to the top level the Photostick USB key directory. The finder will restart, and now if you open your Photostick, you can see the hidden folders! In the "bin" folder, you'll find ThePhotoStick.app (Yes, the actual app!). Expose all the hidden files by pasting in the following command in terminal and pressing enter.ĭefaults write AppleShowAllFiles -boolean true killall Finder But to make it work again, plug the Photostick in, and open a Terminal window on the Mac. Perhaps someone can advise how to correct the alias "auto launching" when the USB key folder is opened. The creators hid the actual MacOS app in the filesystem! So if you don't have an alias to launch it, you never see it, so you can't launch it. Well it won't if you delete the alias file! And the software no longer works as they can't launch it and it will no longer auto-launch as all their support docs say it will. lnk file or alias very easily! It isn't locked! So thousands of folks have accidentally deleted the alias to the. lnk file to the Windows version app, and an Alias to it for MacOS app. However the somewhat clueless folks who make the thing did a poor job. It only executes it when you open the mounted Photostick USB key. The "Photostick" doesn't install the app which is really the heart of the thing. However no one has provided the answer to correct this problem in dozens of posts going back to 2017. No topics were still open on this issue, yet no one actually showed how to fix it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |