Conversation
…dding to objects to the graph, with how graphRenderer was rendering.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 moves the actual calling of syncNodesToScene from the graph
The bug was that sync nodes to scene has a race that a node has EXECUTED to create the object to add to the scene, but execution hasnt occured yet (just connection)
This moves conditional syncing of scene objects to the scene graph, AFTER an execution of newly connected nodes triggers the lazy creation of a Satin Object in a Consumer / BaseObjectNode.
At least this was a surgical change :D