On 'Publish to MuseScore.com' remember the last settings reg. Visibility

[Jojo-Schmitz]

Your idea

On 'Publish to MuseScore.com' remember the last settings reg. Visibility (Public/Unlisted/Private).

Problem to be solved

I find it rather annoying to have to select "Unlisted" time and time again, and that even when the score is just updating an existing one with that setting.

Prior art

N/A

Additional context

Bonus points for fixing the dialog on musescore.com to memorize the setting for "Show parts, if any",and esp. when updating existing scores having used that setting before. Even if that is for another team.

Checklist

• This request follows the guidelines for reporting issues
• I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

[Jessica-IX]

Could you specify on ‘remember the last visibility’?

Do you want the default visibility for the same score to follow its existing visibility on cloud,

or do you want all scores to share a global last visibility (maybe one for publish and another for save-to-cloud),

or do you want a combination of both?

For example, if a score has been published before, then its default visibility should stay the same as its existing visibility.
But if the user is creating a new score, instead of defaulting to Public for publish-to-cloud and Private for save-to-cloud, it should use the visibility that was last used when the user last published or saved a score to the cloud.

[cbjeukendrup]

[Although I don't want to interfere with clarifying this issue, I would advise against working on it in its current state because the internal team has not yet approved it yet]

[Jojo-Schmitz]

I'd want the default visibility for the same score to follow its existing visibility on cloud.
But a global setting would be good too, additionally

[Jessica-IX]

I think a global setting is more suitable for a preference setting feature, while for this issue specifically, default visibility for the same score to follow its existing visibility on cloud is probably the better solution.

Should I post the ideas I shared in our discussion here for the team to see, or submit a pull request and explain it here?

I've already implemented a version that makes the default visibility of the same score consistent with previously released versions.

[Jessica-IX]

I've submitted a PR based on the per-score design and included a document of my more detailed ideas in the description https://docs.google.com/document/d/1FYUVtQuyvbf7FxFApWO06yTbfau6PLvMsaj-jRfR1yE/edit?usp=sharing.
Feel free to take a look! The change only requires deleting an if-condition, so reviewing it should be easy.