-
-
Notifications
You must be signed in to change notification settings - Fork 21.2k
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
Allow EditorExportPlugins to provide export options #72895
Allow EditorExportPlugins to provide export options #72895
Conversation
1f1f1fb
to
a01d903
Compare
a01d903
to
23ed628
Compare
export_plugins.sort_custom<SortByName>(); | ||
|
||
for (int i = 0; i < export_plugins.size(); i++) { | ||
export_plugins.write[i]->set_export_preset(p_preset); |
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 moved this into the ExportNotifier
above, or the options would not get read when exporting for a second time. Not sure why this was set here in the first place.
23ed628
to
6963e84
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.
Makes sense, and the implementation looks good to me.
Thanks! |
@RedworkDE There's a bug with restoring the saved values for the editor export plugin options from the preset; see #78958 (comment) |
Basically duplicates
get_export_options
fromEditorExportPlatform
toEditorExportPlugin
and sets things up for scripting.This allows export plugins to to have export preset specific options that also show up in the export dialog.
Example (the Dotnet options are added from from the CSharpExport plugin):
Open issue: From scripts the options are always added to the very end of the options list so users always have to scroll to the very end to access them