-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add global coordinates broker but keep global cursor transform #791
Conversation
This approach calls Utils.getPointerCoords() (the unified touch broker) when the event starts ONLY. Since the touch tracker fails to update once the event is "adopted" by a widget, we still need to update the global cursor's coordinates. This superficially fixes #764, but REVERT this commit before working on cleaning up touch handling!
5ca1d4f
to
fbca41f
Compare
@Thesola10 let me know if you when you want me to test/review this one. |
@jtaala go ahead! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I switched to PaperWM's signal approach (for consistency and it's also easier to destroy/cleanup - for when/if we add more signals to utils.js.
Give it a final test and I'll merge and do a new release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, merge when ready.
This comment was marked as resolved.
This comment was marked as resolved.
cb8dfbb
to
e05a16a
Compare
This PR functionally fixes #764 but is non-ideal from a code quality standpoint. The cleaner version and discussion around it is and should remain in #766, this PR is a hotfix.