-
-
Notifications
You must be signed in to change notification settings - Fork 22k
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
Reorganize EditorNode menu options #101093
Conversation
FILE_UNDO, | ||
FILE_REDO, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Renamed these 2 for consistency, but it does not look good. Though alternative is that they are the only 2 EDIT options.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can keep them as EDIT_UNDO
/ EDIT_REDO
, that's clearer.
Edit: Ah wait I just understood, these are all entries in the "Scene" ("File"-like, menu). Then I guess the rename makes sense... but yeah it's not great.
FILE_QUIT
also doesn't make too much sense so it's not too bad IMO.
Needs rebase. |
#101094 will conflict again, so I'll wait. |
dcd2d1f
to
d724a06
Compare
This comment was marked as resolved.
This comment was marked as resolved.
d724a06
to
24eadaa
Compare
Thanks! |
Inspired by #59442 (comment)
This PR moves around and renames various enum values from EditorNode. They are now organized by menu, listed in the order they appear, and consistently prefixed: FILE, PROJECT, EDITOR, HELP.
There were various "menu options" that weren't actually menu options, I changed them to methods. There were also some unused enum values, which I removed. I also moved some options used exclusively in scene tabs to EditorSceneTabs (they are still handled in EditorNode).
Some fake menu options were kept, because their logic is a bit tangled. We could rename them to use common prefix.