search

rxhanson / Multitouch-Community

Issue and feature request tracking for the Multitouch app
https://multitouch.app
38 stars 0 forks source link

(Middle) Loss of functionality after system wake #73

Open CartoonChess opened 4 years ago

CartoonChess commented 4 years ago

There's no repo for Middle (that I can find), but it has the same issue of losing functionality on system wake sometimes. Unlike Multitouch, there's no UI option for "Restart on wake" as mentioned in the readme. Is there perhaps a shell command still accessible? Thanks.

rxhanson commented 4 years ago

Thanks for reporting! The default behavior in Middle is to restart on wake, and I left out the checkbox for simplicity.

It's likely that macOS is just not sending touch data to Middle, which would be fixed by waiting longer to restart itself, thereby registering for touch data later after wake.

Try adjusting this value with:

defaults write com.knollsoft.Middle restartOnWakeDelay -int 4

There was some discussion on proper values for Multitouch in https://github.com/rxhanson/Multitouch-Bugs/issues/69

If that doesn't work, let me know and we can take further steps in debugging.

CartoonChess commented 4 years ago

Great! Thanks for the helpful response. I've addd that value (there wasn't one before) and also reviewed the ticket to which you linked. I'll report back after a while with the results.

rxhanson commented 4 years ago

I forgot to mention that you'll want to restart the app after that terminal command.

Also just a side note that the default value is 1 (when there is no value set for restartOnWakeDelay).

rxhanson commented 4 years ago

Just checking back in - let me know if you've had a chance to try it out and if you settled on a value where you don't experience the issue.

In a future release, I'm planning on adding a hidden UI config that sets this value so that a terminal command won't be necessary.

CartoonChess commented 4 years ago

I was still having troubles with 4, so I'm trying 5 from today. Will keep you updated!

CartoonChess commented 4 years ago

Update: After slowly increasing the delay and a safe period of waiting, I'm confident reporting 7 is the value that works for me! Thanks.

rxhanson commented 4 years ago

Thanks so much for posting back!

For future users: I did end up adding a debug/viewer menu config option to toggle a 5 second delay (visible when you hold the option key in the status bar menu), and I think I'll change it to 7 seconds in an upcoming release.