Multitouch version 1.5.3 is now available for download! The main focus of this version is to get a few bug fixes out and to improve the gesture disabling capabilities. These past few versions have come out in somewhat quick succession, and I’m planning on settling back into a published release every two to three weeks.
Previously, the “Disable Gestures” menu item didn’t prevent Multitouch from still processing touch data that went through the system. This would also mean that some gestures were still getting intercepted. For example, force touches would still get intercepted if you had force touch gestures configured in Multitouch. In version 1.5.3, “Disable Gestures” won’t interfere with any default gestures in macOS.
Additionally, I’ve added the ability to disable Multitouch for specific apps via the “Disable Gestures for [Application]” menu item. There’s also improvements on the “rest one tap one” gestures when tap to click is enabled.
In version 1.4.0, I had made a switch to use the private multitouch framework in macOS, and there’s still some work that I have to do to round out this transition. Using that framework means that the touch data I am processing isn’t using Apple’s algorithms for wrist, palm, or thumb rejection. I have built in some initial wrist/palm rejection, but I’m still working on getting the thumb recognition implemented.
If tap gesture recognition isn’t working for you the same as before 1.4.0, you can execute the following command in Terminal to get Multitouch to go back to using the event tap with Apple’s wrist/palm/thumb rejection.
defaults write com.brassmonkery.Multitouch avoidPrivateFramework -bool YES
You’ll have to restart Multitouch for this to take effect. Note that the reason I moved to the private framework is because I had users that reported macOS pinch/rotate, and two finger swipes were not working properly when I was using event taps.
Alternatively, you could wait until I finish my implementation, which is built based on observations of built-in macOS behavior.