Store components state for each entity #82
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Yep. Good idea! I also added small fix to correct set default open from header props. |
|
Work great in my end, feel free to merge |
|
Thanks for the pull request! I plan to finish 0.3 by the end of this week or the middle of next week. Do you have a preference on how you should be mentioned in the release and news for the bevy discord server? |
|
Maybe something like: Should be enough |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an accidental interesting solution for issue #52.
The inspector tab stores the state (open/close) for each component per entity. Which means:
"If entity B has components Name and Transform opened, and you select entity A with other components opened, when you go back to entity B, Name and Transform will still be opened.