It also fixes an issue that prevented Default Folder X from showing recent files and folders in your Dropbox folder if you turned on Dropbox’s syncing of your Documents and Desktop folders. In that configuration, Dropbox syncs your Documents and Desktop folders to a hidden folder within your Dropbox folder. Default Folder X, being the good citizen that it is, saw that hidden folder and said to itself “oh, if you’re putting files and folders into a hidden folder, you probably don’t want them shown in your Recent Files and Recent Folders menus,” and acted accordingly. Now Default Folder X will ignore the fact that that folder is hidden, showing those recent files and folders in its menus.
This beta build also enables DFX in the Flying Logic app and fixes a glitch in the way VoiceOver reads the path menu in Open and Save dialogs.
It’s June, which means Apple has begun rolling out test builds of the next version of macOS, dubbed macOS 12 Monterey. And that means we’ve got a public beta version of Default Folder X available, bringing Default Folder X’s file and folder organization chops to the new OS.
And if you’re not running Monterey yet, version 5.6b1 still addresses some issues with Affinity Designer and other Affinity apps, Photoshop’s “Export As” dialog, and Google Drive.
Version 2.6.3 of App Tamer improves its own efficiency, as well as addressing a few issues that have been brought up by users. When collecting and managing CPU statistics of the processes running on your Mac, App Tamer now uses two additional strategies to reduce its own processor usage. And on Apple Silicon-powered M1 Macs, its helper application (which is in charge of managing the CPU usage of other apps) schedules its work on the M1’s “efficiency cores”, which use less power than the CPU’s “performance cores”.
On top of that, several bugs and user interface issues were corrected to prevent settings for critical processes from being changed to values you really don’t want (trust me 😁), and fixing a rare issue with Amazon Photos.
With the recent focus on Default Folder X’s integration with Path Finder, I’ve been fielding a number of questions about how to make Default Folder X open folders in Path Finder instead of the Finder.
Using Path Finder instead of the Finder for all apps
The first, simplest answer is that Default Folder X uses your “default file browser” when opening folders. If you set your default file browser to be Path Finder, selecting a folder from Default Folder X’s menus will open it in Path Finder. This will also make all other apps on your Mac use Path Finder for their “Reveal in Finder” commands.
“But how the heck do I set Path Finder as my default file browser?” you say. Well, I’m glad you asked! It’s easy – there’s a setting in your Path Finder preferences:
Using Path Finder instead of the Finder – but just for Default Folder X
If you’d rather make this apply only to Default Folder X, you can set Default Folder X’s “fileViewer” preference in Terminal with this command:
Note that if you’re using the Setapp version of Path Finder, you should replace ‘com.cocoatech.PathFinder’ with ‘com.cocoatech.PathFinder-setapp’. To tell Default Folder X to go back to using the Finder instead of Path Finder, just replace ‘com.cocoatech.PathFinder’ with ‘com.apple.finder’.
Toggling between Path Finder and Finder on the fly
And finally, if you want to get really fancy and sometimes have Default Folder X open folders in the Finder and sometimes in Path Finder, you can set up an AppleScript to toggle back and forth. Attaching a script like this to a keyboard shortcut using Peter Lewis’ amazing Keyboard Maestro app makes it super-easy:
-- set the 'currentViewer' variable to the current fileViewer setting set currentViewer to do shell script "defaults read com.stclairsoft.DefaultFolderX5 fileViewer" -- now switch to whichever fileViewer is currently not in use if currentViewer is "com.apple.finder" then do shell script "defaults write com.stclairsoft.DefaultFolderX5 fileViewer com.cocoatech.PathFinder" else do shell script "defaults write com.stclairsoft.DefaultFolderX5 fileViewer com.apple.finder" end if
Version 5.5.9 of Default Folder X is available. One very significant improvement is its “reaction time” to bring up its controls when an Open or Save dialog comes up on the screen.
Under the hood, Default Folder X relies on notifications from macOS to alert it to the presence of a file dialog, and then queries the system to determine the dialog’s characteristics (whether it’s an Open or Save dialog, whether it’s a sheet or window, which folder it’s displaying, etc). In Big Sur, the system’s responses have become slower under some circumstances, resulting in a longer delay before Default Folder X’s controls appear around Open and Save dialogs. Version 5.5.9 streamlines the queries that Default Folder X makes to the system, resulting in a much quicker response after it’s notified that an Open or Save dialog has popped up – it’s nearly twice as fast as previous versions.
And in the process of analyzing Default Folder X’s performance to make it more responsive, I found some inefficiencies in the way it collects and organizes its lists of the windows open in the Finder (and Path Finder and ForkLift, if you’re running those apps). Those inefficiencies have been eliminated as well, reducing Default Folder X’s CPU usage and further improving its response time.
There are also a few fixes in the Finder-click feature to work around a bug in the macOS Finder: Default Folder X will no longer display some tabs of a Finder window as separate windows when the Finder returns incorrect data. In addition, you should now be able to reliably traverse DFX’s menus with the keyboard, and selecting the default folder item in the Favorites menu will work consistently.
Version 2.6.2 of App Tamer is available, fixing a couple of user interface bugs that could trip up new users. When newly installed, the size of App Tamer’s window was much smaller than it was supposed to be, making it hard to see the list of tamed processes. Compounding this was a change in version 2.6.1 that resulted in the mouse cursor not turning into a little arrow when you hovered over the edges of the window, so you couldn’t tell it’s resizable.
Another glitch, a result of changes that Apple made in Big Sur, could result in the names of processes being truncated in the process list. That’s been fixed as well.
An experimental feature for a very specific system problem:
And now for the geeky, experimental feature: It’s come to my attention that some people are living with bugs in macOS that can result in essential background processes (like lsd and pkd) suddenly consuming tons of CPU time and bringing their Mac to a standstill. Despite chasing around to try and find the culprit, they often can’t resolve the problem without completely reinstalling the system. And apparently, App Tamer’s process throttling can’t limit the CPU usage without effectively disabling whatever function those processes are supposed to be performing.
So I’ve added a “runaway process assassin” to App Tamer. You specify which processes to watch, and if the CPU usage of any of them stays above a specified limit for a certain amount of time, App Tamer just kills the process. This certainly isn’t ideal, but works fine for system daemons that macOS will automatically relaunch whenever they’re needed. This feature is probably only useful to a few people, but because it isn’t something that’s easy to code up with an AppleScript or shell script, I figured I’d just add it. App Tamer is already collecting the CPU statistics anyway.
To configure this, you have to use Terminal. Paste in these commands, hitting the Return key after each one:
The first command turns on the killRunawayProcesses feature.
The second sets runawayProcessCPULimit to 50. You can set that to whatever CPU percentage you want.
The third sets runawayProcessTimeLimit to 20. This is how long (in seconds) the process has to be above its limit before App Tamer kills it.
The fourth sets runawayProcessList to watch lsd and pkd. You can add as many processes as you want here, separated by spaces. For full-fledged applications, use the app’s bundle identifier.
When App Tamer kills a process, it will put up a notification to let you know. You’ll probably want to make sure you’ve allowed App Tamer to display notifications in System Preferences > Notifications.
WARNING: Don’t turn this on unless you have a real need for it! You could potentially kill a service that’s necessary for your Mac to operate correctly. However, if you do need and make use of this feature, I’d appreciate hearing from you in the comments or at firstname.lastname@example.org.
For folks that use Path Finder (an excellent Power User’s alternative to the Finder), you’ll be happy to know that Path Finder is now a fully supported alternative when you’re using Default Folder X. Anywhere that DFX integrates with the Finder, it will now use Path Finder if it’s running.
New in this release is the ability to add Default Folder X’s shortcut buttons to Path Finder’s toolbars. This lets you quickly pop up Default Folder X’s menus or slide out its drag-and-drop drawer by clicking a button in the toolbar.
Default Folder X also now “sees” all of the tabs in Path Finder’s windows. Every folder that you have in a Path Finder window will be shown in Default Folder X’s “Finder Windows” menu and highlighted by it’s Finder-click feature in Open and Save dialogs.
For those of you that _don’t_ use Path Finder, this release delivers a bunch of important bug fixes, so please don’t pass it up. Chief among them are fixes for the occasional disappearing cursor in Open and Save dialogs (finally), better reliability when switching between folders, and the elimination of a hang that could occur as Default Folder X was launching.
Download links and a full list of changes are available on the Default Folder X Release Page, or if you’re already running Default Folder X, just choose “Check for Update” from its menu to get the update.
Version 1.8.2 of Jettison is now available. It brings a number of improvements, including several fixes for problems remounting disks after they’ve been ejected.
Jettison’s error reporting has also been improved so that it catches edge cases where a disk unmounts after Jettison has been told by the system that the unmount failed. This should prevent those error messages that said a problem had occurred, but then didn’t list any disks in the error details.
For several releases now, Jettison has been quietly quitting Photos, iTunes and Music before it ejects disks, then relaunching them when those disks are remounted. This prevents problems for the many people that keep their photos or music on external drives. In doing this, however, Jettison was a little too aggressive: It quit the apps when you chose “Eject External Disks Now” from its menu as well as when the machine went to sleep. That turned out to be a Bad Idea, so now it’s only done before ejecting disks when the machine is actually going to sleep.
In a similar vein, there are now some preference settings accessible via Terminal to tweak this behavior. You can turn off the auto-quit / relaunch behavior using this command in Terminal:
where a whitespace-separated list of process names goes in place of photoanalysisd.
And yes, if these options prove popular, they’ll get their own place in the preferences dialog so you no longer have to use Terminal to set them up.
So anyway, this is available in Jettison 1.8.2, with details and download links on the Jettison Release Page. Or if you’re already using Jettison, choose “Check for Updates” from its menu in your menu bar.
Version 2.6.1 of App Tamer is now available! This maintenance release of our app for taking control of your Mac’s CPU and battery delivers a number of bug-fixes. It works correctly with the Origin game launcher, as well as with processes that are launched using ‘sh’ and ‘tcsh’ shell scripts (which some ‘normal’ applications do under the hood).
App Tamer 2.6.1 also prevents you from completely stopping apps that are distributed via the Setapp subscription service because that can cause issues with Setapp. If you want to reduce the CPU usage of those apps, simply have App Tamer throttle them to 1% CPU rather than completely stopping them.
And finally, this release allows you to make App Tamer’s process window smaller than its default size and keep it that way. Previously, it’d insist on enlarging the window back to its default size when you closed it and opened it again. Oops 🙄