Skip to content

Conversation

@andyfinnell
Copy link
Collaborator

Summary

hierarchyDisplayDidFinish is currently called when a node's immediate subnodes implement custom CALayer rendering. For example, ASNetworkImageNode and ASTextNode perform this sort of rendering. However, it can be useful -- and less fragile -- if hierarchyDisplayDidFinish is propagated further up the node hierarchy. That way, if a feature is refactored such that an extra node appears between the node implementing hierarchyDisplayDidFinish and the nodes doing CALayer rendering, we don't lose the callback.

Test plan

Manually tested using a modified version of the Kittens example. Also ran build.sh tests.

## Summary

`hierarchyDisplayDidFinish` is currently called when a node's immediate subnodes implement custom CALayer rendering. For example, ASNetworkImageNode and ASTextNode perform this sort of rendering. However, it can be useful -- and less fragile -- if `hierarchyDisplayDidFinish` is propagated further up the node hierarchy. That way, if a feature is refactored such that an extra node appears between the node implementing `hierarchyDisplayDidFinish` and the nodes doing CALayer rendering, we don't lose the callback.

## Test plan

Manually tested using a modified version of the Kittens example. Also ran `build.sh tests`.
@andyfinnell andyfinnell requested a review from rcancro May 8, 2025 18:53
@rcancro rcancro merged commit e894389 into TextureGroup:master May 8, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants