-
-
Notifications
You must be signed in to change notification settings - Fork 108
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
fix: raycaster does not work properly when scene is not in full screen #304
Merged
alvarosabu
merged 21 commits into
main
from
bugfix/282-raycaster-does-not-work-properly-when-scene-is-not-in-full-screen
Jun 19, 2023
Merged
fix: raycaster does not work properly when scene is not in full screen #304
alvarosabu
merged 21 commits into
main
from
bugfix/282-raycaster-does-not-work-properly-when-scene-is-not-in-full-screen
Jun 19, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…does-not-work-properly-when-scene-is-not-in-full-screen
…when-scene-is-not-in-full-screen
…iewport fix: onPointerMove does not fire too often anymore
5 tasks
✅ Deploy Preview for tresjs-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Tinoooo
changed the title
Bugfix/282 raycaster does not work properly when scene is not in full screen
fix: raycaster does not work properly when scene is not in full screen
Jun 16, 2023
…when-scene-is-not-in-full-screen
alvarosabu
approved these changes
Jun 19, 2023
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.
Thanks a lot, @Tinoooo amazing work 👏🏻
…does-not-work-properly-when-scene-is-not-in-full-screen
Tinoooo
deleted the
bugfix/282-raycaster-does-not-work-properly-when-scene-is-not-in-full-screen
branch
June 19, 2023 15:27
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes
pointerMove
does now trigger only when the mouse actually moves, not on everyrequestAnimationFrame
callback.click
event behaves now just like in the DOM. That is only ifpointerup
fired on the same element aspointerdown
did before. The click event used to fire in the same cases aspointerup
would fire.Breaking Changes
pointerLeave
event does not provide an intersection object, since leaving means no more intersection. 😄