Initialize views in front end code #54
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
Split view initialization into two steps; we can't initialize the scene tree until we know where the node is going to be initially placed, but the backend code doesn't know how to do that. Also add additional functions that allow a view's size and location to be set.
Add view callbacks and use them to initialize views in the lisp code. The view lists added to the state object might not stick around and were added for illustrative purposes
sdilts
force-pushed
the
feat/init-view-in-frontend
branch
from
e983b4b to
55aa87c
Compare
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 allows us to place the views where we need them instead of having them get placed first, then moved.