-
-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Add an Advanced Options
toggle to the editor export preset
#88419
Add an Advanced Options
toggle to the editor export preset
#88419
Conversation
f56763a
to
3e39a95
Compare
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.
Thanks, this looks awesome!
The code looks good - just two little comments. Seemed to work great in my testing too. :-)
return; | ||
} | ||
advanced_options_enabled = p_enabled; | ||
EditorExport::singleton->save_presets(); |
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.
Why do we need to save the presets when this is changed?
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 followed the pattern used for runnable
; from reading the code, we persist metadata about a preset everytime it's modified, so I did the same for this new field.
c6135dc
to
846652e
Compare
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.
Looks good to me! I just retested it, and it's especially nice on top of the changes from PR #88297 because this exposes the new advanced Gradle template fields :-)
I think Runnable should be placed on top of Advanced Options, instead of the other way around. This way, Advanced Options will be closer to the view it affects (the list of export options). |
It does peeve me that it occupies a whole new line instead of being alongside the "Runnable" toggle. I understand why that is, but it does look odd. |
d87cd5d
to
5c4f845
Compare
@Mickeon I played around with keeping them on the same line. Let me know what you think |
I do like it myself, but it may break a few editor UX rules. @Calinou may know best. At worst it is reverted. |
Putting them side-by-side is ideal to me 🙂 I was concerned you could confuse the two buttons together (since the checkbutton icon that appears on the left of Runnable could be confused to be for that setting). However, I'd say the different text color when the button is checked makes it unambiguous enough. If there's a strong need, we can have an Separator node placed between the two buttons, but I think this is good to go as-is for now. |
5c4f845
to
6ef3154
Compare
Thanks! |
Similar to the
Project Settings
, add anAdvanced Options
toggle to the editor export presets to allow hiding advanced options and simplify the UI.Follow up of the discussion with @dsnopek on #88297 (comment).
This PR sets up the infra and hides Android advanced options; other platform maintainers can leverage the same logic to hide options they deem advanced for their platform.
Screen_Recording_20240216_141113_Godot.Editor.4.debug.mp4