You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default file name is the same as the title if you specify the title in the New score dialog:
However, if the title contains characters that are prohibited (for Windows, see Naming Conventions), such as double quotes, this will not allow you to save the file - the error "The file name is not valid" will appear:
It is important to note that from the message it is not clear which symbols are invalid.
Musescore should also check the file name at the stage of clicking on the "Save" button and display an informative message if the file name contains prohibited characters.
Problem to be solved
Not to confuse the user with uninformative messages
IIRC Mu3 did that.
BTW: On renaming a file in Windows Explorer this is shown:
Under macOS and Linux these are all allowed (except for /), as far as I can tell, but using them there isn't a good idea either
Filtering those out may not be needed, but a meaninfull error message (like the above from Windows) definitely is.
And maybe a warning about them on macOS and Linux.
Your idea
The default file name is the same as the title if you specify the title in the New score dialog:
However, if the title contains characters that are prohibited (for Windows, see Naming Conventions), such as double quotes, this will not allow you to save the file - the error "The file name is not valid" will appear:
It is important to note that from the message it is not clear which symbols are invalid.
Musescore should also check the file name at the stage of clicking on the "Save" button and display an informative message if the file name contains prohibited characters.
Problem to be solved
Not to confuse the user with uninformative messages
Prior art
No response
Additional context
This issue is based on a report from https://musescore.org/en/node/375422
Checklist
The text was updated successfully, but these errors were encountered: