Skip to content

4.6.0 ports #29326

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 15 commits into from
Aug 18, 2025
Merged

4.6.0 ports #29326

merged 15 commits into from
Aug 18, 2025

Conversation

cbjeukendrup
Copy link
Member

cbjeukendrup and others added 15 commits August 18, 2025 16:59
* When you press the mouse down, the pasted range will initially be placed at the same measure alignment as the source material
* When you then start moving, the position of the mouse becomes the start position for the pasted range.
- Created initial test case for Issue 19571
- Updated test case with improved validation
We can't assume that all (custom) SMuFL font meta data files are complete and valid.
When an Ambitus is created, it has by default no tpcs set. In the layout code, this situation is handled by placing the notes on the top and bottom staff line. The `accessibleInfo` method did not take this situation into account, and called `tpc2name`; the "inner" tpc2name method has a stack buffer overflow when an invalid tpc is passed in.
Resolves: musescore#29187

Also makes those buttons slightly more compact, for consistency with the rest of the app.
lupdate appears to depend on things from `qtdeclarative`. The gain of not installing all archives is small, so let's not risk breaking anything again in the future and let's just install all archives.
This appears to be a Qt bug which is triggered by a property alias
pointing to a property of an item which is referenced via another
property alias. (https://bugreports.qt.io/browse/QTBUG-124476)
* tweak copy
* don't show on single-staff instruments
* disable when "never hide" is selected
Resolves: musescore#29267

And some spacing issues, and some texts that might potentially be cut off due to hardcoded widths...
…tempo

Fix playback tempo when creating new score
@RomanPudashkin RomanPudashkin merged commit 569e432 into musescore:4.6.0 Aug 18, 2025
13 checks passed
@RomanPudashkin RomanPudashkin deleted the port/4.6.0 branch August 18, 2025 16:11
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