Change mouseX/mouseY handling #1471
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
This changes the way mouse and touch values are stored to address the following two tickets:
#1176
#1269
Currently,
mouseXandmouseYvalues are always lagging behind the real system values when the mouse is moving.The new approach works like this:
mouseXandmouseYvalues so that they represent the actual mouse value at that eventdraw()a frame, we set thepmouseXandpmouseYto the value ofmouseXandmouseY, the next time the draw is called it will have the previous mouse positionmouseXandmouseY, we also set thepmouseX/pmouseYto the same value. This way they don't start at (0, 0) which is a bit arbitrary.pwinMouseX/pwinMouseYSome tests, I'm using the p5js editor.
Example 1
Before PR:

After PR:

Example 2
Before PR:

After PR:

Let me know what you think! 😄