musescore / musescore/MuseScore
Dots on dotted notes/rests are not correctly synchronised between parts and main score
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
Engraving bug (incorrect score rendering)
Description with steps to reproduce
Dots in parts don't obey the Synchronise with main score toggles when these are set to ON (default).
- Select a dotted note in main score
- Set it as invisible
- View corresponding part
Expected behaviour: note head and dot should be invisible in both main score and corresponding part (provided style/appearance is set to synchronise with main score)
Actual behaviour: the note head is correctly shown as invisible, but the dot remains visible even though the style/appearance synchronisation toggle remains ON. Changing the dot to invisible in the part does not automatically turn the dot's style/appearance synchronisation toggle to OFF.
Dots similarly ignore the position synchronisation toggle when set to ON (eg. adjusting horiz-offset rather than visibility)
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
4.6.5
Regression
I was unable to check
Operating system
Arch linux (x86_64)
Additional context
If the part is only initialised after the dotted note is set invisible in the main score, then initially the part correctly shows both note head and dot as invisible, but any subsequent main part changes behave as described above, unsynchronised.
Dots on rests and note heads of all durations are affected similarly.
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
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.