We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Right now, for our examples like AutoComplete, we just bind directly to the raw GLFW / window events.
This isn't ideal, because for things like focus management to work, we need to control the 'bubbling' of events across the node 'hierarchy'.
We should implement a handleEvent method on our Node hierarchy, and add the following event types:
handleEvent
KeyDown
KeyPress
KeyUp
MouseDown
MouseUp
These are events that we'd bubble through our node hiearchy, and then expose as handlers on the primitives / component tags.
The text was updated successfully, but these errors were encountered:
The infrastructure for this was implemented in #117 - closing in lieu of more specific / actionable work 😄
Sorry, something went wrong.
No branches or pull requests
Right now, for our examples like AutoComplete, we just bind directly to the raw GLFW / window events.
This isn't ideal, because for things like focus management to work, we need to control the 'bubbling' of events across the node 'hierarchy'.
We should implement a
handleEvent
method on our Node hierarchy, and add the following event types:KeyDown
KeyPress
KeyUp
MouseDown
MouseUp
These are events that we'd bubble through our node hiearchy, and then expose as handlers on the primitives / component tags.
The text was updated successfully, but these errors were encountered: