Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Should maybe_changed always match at least once? #270

Open
swiftcoder opened this issue Jul 21, 2021 · 0 comments
Open

Should maybe_changed always match at least once? #270

swiftcoder opened this issue Jul 21, 2021 · 0 comments

Comments

@swiftcoder
Copy link

I have a system that is using #[filter(maybe_changed::<Foo>())] to update lazily. However, I'd like to run this same function once to set the initial state correctly. Is there a filter I can combine to always execute on first encountering a given component, or a way to set the dirty flag on the component during initialisation?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@swiftcoder