Implement hidden class in core to replace "EditorX" class being hidden. #90765
+53
−38
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
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
fire
changed the title
|
What's the difference between a hidden class and an internal class? Would it be feasible to use internal classes instead of adding a new kind of class? |
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.
Fixes #88601
This create a way in
ClassDBto mark a class as hidden. This value is then used by Create Dialog to skip those class. All Classes that started withEditorwere marked as hidden to match previous behavior.The goal would be to add a similar thing in ScriptServer to enable a
@hideannotation to do the same for a script which would help for godotengine/godot-proposals#1047I would wait for the ScriptServer counterpart which I am already working on before merging because this in fact remove the posibillity to hide nodes even if it was never really considered a feature.
This should make hiding nodes available to GDExtension at least I think.