musescore / musescore/MuseScore
An unset autoplace property gets lost on Mu3 import
Open
@mathesoncalum is already working on this.
Since Oct 6, 2023.
P3
regression MS3
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UI bug (?)
Bug description
No response
Steps to reproduce
- Take a Mu3 score that has some element (e.g. a staff text) with autoplace being disabled, and some offset applied
- Import into Mu4
- Notice that Autoplace is enabled for those elements, the offsets though are still there and in effect!.
Screenshots/Screen recordings
No response
MuseScore Version
4.1.1
Regression
Yes, this used to work in MuseScore 3.x and now is broken
Operating system
Windows 11
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.