New Export dialog (pdfs etc.) has too many steps
Reported version
3.x-dev
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.0.395303918, revision: github-musescore-musescore-
The old export dialog involved clicking on the "Export" option then "Save". However, at least for pdfs, the new export process represents a loss of utility because it adds up to three extra steps: (1) The export dialog, (2) an "export successful" dialog, and (3) an extra save confirmation if the file exists already (in addition to the Windows confirmation).
Fix version
3.6.0
Comments
It has more steps for sure, but also more options.
I think these export settings are about as well placed as they could be. It makes zero sense for them to be hidden in 'preferences'.
I'd also point out that exporting is not a very common action (compared to, say, adding a slur mark, or pressing Undo). For most people, this is something they'd do once they've accomplished a significant amount of writing. For this reason, I think it is completely acceptable to add this extra step. It's also a very common flow (witness any Adobe or 3D app export settings, as well as export settings in apps like Logic Pro).
I do agree that the 'Export successful' dialog is unnecessary though.
I do export a lot. But there's Batch Convert for the rescue ;-)
I think it would be reasonable to have the default options set so you can choose Export then hit enter and you would get a PDF export of the currently viewed score as you currently do.
Just a reminder about the other issue: the "Confirm replace" dialog which duplicates the "Confirm save as" dialog.
The extra confirmation dialog was discussed on Telegram so it'll be taken care of.
PR created! https://github.com/musescore/MuseScore/pull/7019
(by the way, in principle, indeed all (default) settings are loaded, so you can just hit Return if you quickly want to export.)
Fixed in branch 3.x, commit 1f0c7ee0f1
_Fix #313886: Streamline user experience regarding Export
be exactly as the user types in the SaveDialog, so therefore, we
can have the SaveDialog responsible for asking whether the user
wants to replace any existing files.
will be synced between the ExportDialog and savePng and saveSvg
(by having them use a pointer to the same SaveReplacePolicy), so
that the user won't be asked again the same question._
Automatically closed -- issue fixed for 2 weeks with no activity.