musescore / musescore/MuseScore

Switch to Score tab immediately when opening a score, to make it seem more responsive

Open
#25,100 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Your idea

Currently, the order of operations seems to be:

  1. User clicks score to open it
  2. Processing processing processing processing...
  3. Score tab appears, with score loaded

The lack of visual feedback after step 1 makes it feel like the app is slow to respond to user actions, and you don't really know if it's doing anything or that you have to click again.

I propose to change the order to:

  1. User clicks score to open it
  2. Score tab appears, albeit still empty -> the immediate visual feedback will make it feel more snappy
  3. Processing processing processing processing... (perhaps with progress indicator in the future)
  4. Score appears in canvas
Problem to be solved

I think this would be an easy way to make the app feel snappier without spending ages on trying to improve the actual performance and then come to the conclusion that there is not much that can be done because opening a score is simply a big operation.

Prior art

No response

Additional context

The only potential downside that I can see is: When there is an error, and the score cannot be opened, that would mean that the user would end up with an error message on an empty Score tab rather than the Home tab. But that's really a non-issue, IMO.

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

No files, tests, or entry points are named. Start by tracing the score-opening flow from the reported click action, then verify that the Score tab appears before loading completes and that failures still show an error.

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.