Skip to content

Conversation

Resolves: musescore#30273

Save & restore the custom colors of the `QColorDialog`.
Qt versions before 6.9 saved these per user in a `QSettings`
instance under the organization name "QtProject". This functionality must
be replaced by client code (us). Legacy values are read and used as
default values.
@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Nov 5, 2025

As far as I can tell the vtest failures are expected and happened to the origunal PRs too
courtesy-jump-section-1-1 diff
ornament-4-1 diff
ornament-11-1 diff

@mike-spa
Copy link
Contributor

mike-spa commented Nov 5, 2025

@Jojo-Schmitz thank you! While you're at it, may I bother you to add #30771 as well?

@Jojo-Schmitz
Copy link
Contributor Author

Jojo-Schmitz commented Nov 5, 2025

@Jojo-Schmitz thank you! While you're at it, may I bother you to add #30771 as well?

That seems to be in already!?!

Jojo@DodekaCore MINGW64 ~/Documents/GitHub/MuseScore (4.6.4-ports)
$ git cherry-pick a848ac4
Auto-merging src/engraving/rendering/score/measurenumberlayout.cpp
On branch 4.6.4-ports
Your branch is up to date with 'origin/4.6.4-ports'.

You are currently cherry-picking commit a848ac488c.
  (all conflicts fixed: run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

nothing to commit, working tree clean
The previous cherry-pick is now empty, possibly due to conflict resolution.
If you wish to commit it anyway, use:

    git commit --allow-empty

Otherwise, please use 'git cherry-pick --skip'

Seems you did it already in ac965a2, actually I did it in this very PR here?

Mystery solved: I misstyped the PR number in the PR message, corrected now

I don't quite understand why that PR fixes it only for measure numbers above, i.e. why the same issue won't happen for measure numbers below?

@Jojo-Schmitz Jojo-Schmitz force-pushed the 4.6.4-ports branch 2 times, most recently from 3f9229e to f505cd3 Compare November 6, 2025 16:07
@cbjeukendrup cbjeukendrup requested a review from mike-spa November 6, 2025 16:32
@mike-spa
Copy link
Contributor

mike-spa commented Nov 7, 2025

I don't quite understand why that PR fixes it only for measure numbers above, i.e. why the same issue won't happen for measure numbers below?

Good point, hadn't thought of it (because it's a lot less common), I'll do it in a next PR (or feel free to do one yourself). Meanwhile I'll merge this, thanks!

@mike-spa mike-spa merged commit 9384599 into musescore:4.6.4 Nov 7, 2025
12 of 13 checks passed
@Jojo-Schmitz Jojo-Schmitz deleted the 4.6.4-ports branch November 7, 2025 10:00
@Jojo-Schmitz
Copy link
Contributor Author

See #30911

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants