It’s simply difficult to learn something when the outcome of your actions is delayed.
On a slightly unrelated note, I strongly believe that many people didn’t realize the reason for their discomfort from using a mouse with macOS wasn’t the quirky acceleration algorithm per se, but the input lag which made the algorithm a lot harder to get used to. For many years it had been lagging for 16 milliseconds compared to Windows, and SmoothMouse was the only solution to this problem. Yes, the lag of 16ms may be noticeable by the human eye when combined with the display lag. The top priority was to improve the response time of the mouse pointer in macOS. SmoothMouse wasn’t created only to “fix acceleration”. It wasn’t our top priority back in the day. We filed a bug report in 2014 (#21909158), emailed various Apple employees including Craig Federighi, without any results. Of course, we knew about those problems, but we couldn’t fix them, because they were all caused by a serious bug within IOHID. “IOHID” (deprecated in Sierra) had a lot of problems too, but performance was not one of them. Quite possible you’ve seen SmoothMouse causing crazy things to happen in Steam games or while in Screen Zoom mode-when you pressed a mouse button. To our surprise, those weren’t only games, but also a plethora of professional applications like Ableton, Traktor, Cinema4D etc. The second worst problem was that it didn’t work well with the applications that needed to take control of the mouse pointer. CGEventPost would make SmoothMouse skip movements when your computer was doing graphically intensive calculations. #CONTROLLERMATE WINDOWS 10 FULL#
The recommended API called “CGEventPost” (a part of Quartz) is full of problems. We know this from our experience, because we used CGEventPost in SmoothMouse in 2012–2013 before switching to IOHID. The worst problem was performance.In Sierra, Apple has deprecated “IOHID”, the API SmoothMouse uses to move the mouse pointer.
0 kommentar(er)
