-
-
Notifications
You must be signed in to change notification settings - Fork 98
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.
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
More aggressive walk function #665
Comments
Current function is already pretty aggressive and has minimal dependencies on object methods? What it doesn't do is allow you to prune the walk. |
It still relies on |
true, but we have so little design on "can opt out of event dispatch", i wouldn't worry about it. |
Then how about we change the scope of this to having the current walk step around game objects that don't implement walk? |
The current walk is fine as is, but we need a walk implementation that doesn't care if the child has its own walk method so that the renderer itself can be sure to reach all renderable objects.
We can call the new method
render_walk
for now (unless someone has a better idea) and it should only care that each level has children. It can use therender_walk
method to get the child and grandchildren, but has to work with the case thatrender_walk
isn't implemented.Part of supporting #577
The text was updated successfully, but these errors were encountered: