-
Notifications
You must be signed in to change notification settings - Fork 22
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 Click (Magic Remote) Support #179
Comments
IMHO there shouldn't be "click" handling in its literal form, the Lightning 3 renderer doesn't directly interact with input devices for key input and neither should it for anything else. This should come from the framework that implements the renderer. Whether it is touch, a (magic) mouse, spatial input or neuralink the only thing the renderer will need to answer is what node(s) intersect with a set of coordinates. That way, touch, hover, mouse, spatial, etc can all be implemented in a universal way. @erikhaandrikman you once created a touch library with a bunch of hitbox/intersection logic. We can start with something as basic as L2 and expand it based on the more advanced ones we did in the L2 automotive PoCs. |
Yes - We'd need some API which is "What node is on top at X, Y coordinate" and the framework could ask for that on click events. |
You need a way to omit some nodes from the x/y lookup. |
Do you have this feature planned? |
For magic remote users lets add click handling.
The text was updated successfully, but these errors were encountered: