-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Make use of observer system for input changes #102
Comments
alexparlett
pushed a commit
to alexparlett/sickle_ui
that referenced
this issue
Sep 3, 2024
* Add events for inputs * Publish triggers on changes
alexparlett
pushed a commit
to alexparlett/sickle_ui
that referenced
this issue
Sep 3, 2024
alexparlett
pushed a commit
to alexparlett/sickle_ui
that referenced
this issue
Sep 3, 2024
* Add observe to ui_builder * Fix linting
eidloi
pushed a commit
that referenced
this issue
Sep 3, 2024
* Add events for inputs * Publish triggers on changes
eidloi
pushed a commit
that referenced
this issue
Sep 3, 2024
* Add observe to ui_builder * Fix linting
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the introduction of triggers and observers, instead of having to create a
Changed<X>
system which may or may not have the value changed and could be other reasons (i.e.is_open
on dropdown), use bevy'scommands.trigger_targets
to allow observing on the root entity to allow specific reactions to inputs changing.The text was updated successfully, but these errors were encountered: