Ability to climb up the parent tree for widget blueprint hooking #326
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
Previously, when the parent type is "Indirect (Child)", you could only choose the direct parent for the widget to attach the new widget to. Now you can choose the grandparents too.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously, when the parent type is "Indirect (Child)", you could only choose the immediate parents of the widget variables for the widget to attach the new widget to. Now you can choose the grandparents too.
For instance, if the widget looks like this,
there was no (easy) way to add a widget to the vertical box or the overlay.
With this pull request, you can choose them like this.
