This repository has been archived by the owner on Nov 2, 2021. It is now read-only.
Add bindings for SceneGraphIterator #2
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
violinyanev
approved these changes
Jun 10, 2019
Signed-off-by: Daniel W. S. Almeida <[email protected]>
violinyanev
force-pushed
the
scene-iterator
branch
from
ae3e07c to
5beed80
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 should make it easier inspect RAMSES scene graphs on Python's side.
There's a problem though: I am unsure on how to cast nodes to their most derived type in Python, since a "RamsesPython.Node" is not very useful.
This person has had the same issue.