musescore / musescore/MuseScore

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

Open
#30,850 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs design
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

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. Mu3 BTW does not have that issue

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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the “Publish to MuseScore.com” dialog and its handling of Visibility choices. Make the selected Public, Unlisted, or Private setting persist for later publishes and updates, then verify that reopening the dialog restores it; the optional “Show parts, if any” behavior is noted as a separate MuseScore.com concern.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.