Or if you’re already running Default Folder X, just choose “Check for Update” from its menu in your menu bar. Release notes and download links are on the Default Folder X release page. Various bugs have also been fixed in the way Default Folder X handles Finder comments, cloud-synced folders, the icon of the Finder itself, and Save dialogs in macOS Sierra. They sometimes wouldn’t be recognized by the Finder-click feature because, in my drive to get the best performance, there was a case where I just optimized them out of existence. This method gives you the best access to your Finder windows while still allowing you to move the window (even though the new sheet UI implies that you can’t move it by graying it out).Īnd while we’re discussing Finder-click, version 5.6.5 fixes a problem with the way Default Folder X tracked the windows of Path Finder and ForkLift. The “Downloads” window in the Finder is shown darkened behind a Save As sheetĬlear as mud, right? I’ll be the first to admit that it looks damned weird, but given that the Big Sur / Monterey implementation of sheets is a giant step backward in usability, I didn’t have a lot to work with. Posted in App Tamer, Big Sur, Catalina, El Capitan, High Sierra, Mojave, Monterey, Sierra, Ventura, Yosemite | No Comments » This update is free if you’ve already purchased an App Tamer 2.x license. So that fix is now available in App Tamer, making it a reliable source of CPU information for all processes again.Īs usual, release notes and download links are on the App Tamer release page, or if you’re already using App Tamer, just choose “Check for Update” from its menu. Some hunting around in the macOS source code (thank you Apple for making darwin Open Source!) revealed an alternate method that correctly reports the CPU usage of all processes, including kernel_task. In App Tamer’s defense, the system’s approved public API was supplying those numbers and it dutifully reported them without prejudice. App Tamer would show either zero or astronomical values for kernel_task’s processor use, neither of which was correct. Second, internal changes that Apple made in macOS resulted in App Tamer reporting the CPU usage of one particular process – kernel_task – incorrectly. Unfortunately, it also did that on pre-Big Sur systems, often making its icon too close to adjacent ones in the menu bar. Version 2.7.3 of App Tamer is now available, fixing a couple of problems.įirst, my apologies to folks using versions of macOS older than Big Sur: Changes in the last App Tamer update tightened up the spacing of its menu bar icon to comply with modifications Apple made to Monterey and Big Sur.
0 kommentar(er)
