- User Since
- Jun 2 2019, 7:50 AM (77 w, 6 d)
Oct 25 2019
I haven’t had time to look into this further, other than to determine that sidecar consistently pairs the events. When you touch the screen you get a tablet prox event saying you moved to the screen followed by a mouse down. Then, later, a mouse up followed by the tablet prox event showing you moved away.
Oct 9 2019
Good catch. I was looking for something like dispatchEvents() yesterday but couldn't find it.
Oct 8 2019
I can confirm that if I comment out tabletPoint and tabletProximity in WindowCocoaView, the problem goes away. The mouse up messages have tablet information so pressure get released as appropriate. This was just a test; those events are important for tablets with proximity sensors. Also, I found that later events (like window deactivation) were showing tablet events, which would clearly not be the right thing.
I've got a partial answer for what's going on -- will try to pick this up again tomorrow night, but thought I'd pass on some notes.
The same issue happens in the release version of Catalina with Sidecar and an iPad Pro/Apple Pencil.
Jun 2 2019
Confirmed; the June 1 build fixed this.