An API quirk seems to exist in RealTimeStylus where tips and buttons all share a global "pressed-ness" state - this manifests quite poorly in the current implementation as any barrel button interactions sending many spurious events for other buttons and Up/Down state leaving the tool in an unintelligible state until moved out and back in.
An API quirk seems to exist in
RealTimeStyluswhere tips and buttons all share a global "pressed-ness" state - this manifests quite poorly in the current implementation as any barrel button interactions sending many spurious events for other buttons and Up/Down state leaving the tool in an unintelligible state until moved out and back in.