It currently implements about 90% of Fetch 5.7.7’s features with about 50% of Fetch 5.7.7’s reliability. Fetch 5.8 is now in beta testing you can sign up to test it here. But I wasn’t quite ready to say goodbye, and it occurred to me that there was a third option, something between finishing Fetch 6 and letting Fetch die: I could port Fetch 5.7’s Carbon user interface to Cocoa and make a 64-bit Fetch 5.8. DragThing had features - like the ability to create custom palettes that only appeared in a certain app - that I don’t know how one would replicate today.Īpple had made it clear that 32-bit apps like Fetch 5.7 weren’t long for this world, so it looked like the time had come to lay Fetch to rest for good. I haven’t used DragThing in many many years, but for a long time it was essential to my workflow, and I firmly believe it was a much better launcher than Apple’s own system Dock ever has been. We are sorry to say, DragThing has launched its last app. It will no longer run if you update to Catalina, and there are no plans to make a new version that will. Not that I’m updating from macOS 10.12 to 10.15 super soon, but I’m looking at the non-64-bit apps and worryingĭragThing is written using the 32-bit Carbon APIs that Apple have now removed in macOS 10.15 Catalina.
It won’t show you anything about the state of apps you have in the cloud, via app stores like the MAS, Steam, etc. Important macOS Catalina upgrade tip: Remember that checking your Mac hard drive for 32-bit apps only reveals the apps that won’t work which you have installed. You should be aware of that before you upgrade. However, if your apps haven’t been updated, they won’t run on the new operating system. Chances are your apps have already been updated to take advantage of the architecture. Apple has been talking to developers about the 64-bit transition for several years. For those that have been following along, 64-bit is not that new.
0 kommentar(er)
