Fix event propagation to child after set_as_toplevel #67507
Merged
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.
In certain conditions events did not get propagated to
Control
-childs ofNode2D
-nodes when setting a parent of theNode2D
to toplevel because the Controls did not get added as root-control-nodes in the Viewport.fix #42822
Analysis of the problem is available here: #42822 (comment)
This patch makes sure that such Control nodes become root-control-nodes in the Viewport.
This is done by propagating the info that toplevel status has changed on a parent to all descendant
CanvasItems
passing throughNode2D
nodes and executing the code ofNOTIFICATION_EXIT_CANVAS
andNOTIFICATION_ENTER_CANVAS
on all first reachedControl
nodes.