-
Notifications
You must be signed in to change notification settings - Fork 24
feat(View): pointerSize property #26
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
Conversation
|
Make sure the xy are ints. |
6411b88 to
1b4759c
Compare
|
No luck :-( |
1b4759c to
af7e15d
Compare
|
What are the symptoms of the issue? |
|
No selection happens at all. |
|
Be aware that by changing x1/x2 to be different you will always get a frustrum rather than a ray. You may need to fix/extend the pick method to still perform the ray. Maybe by adding a bool arg for isFrustrum. |
|
Sorry I think I don't have enough knowledge on the matter to be helpful here :-( |
|
af7e15d to
3e2fe54
Compare
|
Same code as before except the condition to detect if it is a click/hover=ray vs select=frustum is not based on the fact that x1 != x2. Otherwise you are changing the behavior of the selection. |
|
Thanks, it works now 👍 |
|
You still need to fix the ray so it is at the center of the x1/x2/y1/y2 and not on one of the corner of the area. |
3e2fe54 to
b30258a
Compare
|
See my code snippet vs original |
b30258a to
bd07c37
Compare
bd07c37 to
d370e94
Compare
|
All working? Ready to merge? |
|
The ray/frustum part are only info metadata and don't affect selection. Maybe the returned array from hover is bigger than 1 and you always pick the first one? Check what the selection returned array looks like? |
|
I think it's just an optical effect due to the pointer shape, I enlarged the pointer area and it actually looks good 😇 |
|
🎉 This PR is included in version 1.6.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |

I'm trying to understand why these changes aren't working, as soon I set a pointerSize larger than 0 picking stops working 🤔