This is confusing behavior from macOS to say the least, but if that works out well for you then that's great.īy avoiding private frameworks, this means that Multitouch is using an Event Tap and receiving touch data from Apple's "supported" way. I'll post an update when I have one available for download. This could take a few tries to get right, and probably some debug builds. In order to implement the automatic restart or reinitialization of the app when touches are not sent to Multitouch, I'll have to determine that touches are existing but are not making it to Multitouch. Although I could be wrong, this appears to to be one of those issues that only affects a handful of users - making you a lucky one :) I'm thinking that this is not directly related to the changes that I put into v1.8, although there's a bit of robustness I can improve there based on things I've learned since. The Multitouch side fix could end up being an automatic restart of the app when touches are not being recognized (kind of ugly). Knowing whether or not it's Apple's problems doesn't change the fact that I'll have to build in some kind of fix on Multitouch's side, but it's good to know in case I can rip out any fix Multitouch side in the future. If you're still having the issues, then at least we know the root of it is in Apple's hands and may be fixed altogether by Apple at some point. Try disabling launch on login on Multitouch, closing it, then logging out and logging in (or restarting your mac). If you don't mind, it would be nice to see if somehow Multitouch is causing these issues with the built-in gestures. Here's a thread on macrumours where people are having similar issues, even without any gesture apps installed:
0 Comments
Leave a Reply. |