musescore / musescore/MuseScore
Invisible notes affect bar width
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
- Create 4 bars.
- Fill the first one with lots of invisible notes.
- Turn off View > Show > Show invisible
Current: The first bar is much wider than the other bars.
Expected: All four bars are the same width.
Changing the bar's "layout stretch" to 0.1 had no effect.
Supporting files, videos and screenshots
Due to these invisible notes:
In which versions of MuseScore Studio is this issue present?
OS: macOS Ventura (13.6.3), Arch.: arm64, MuseScore Studio version (64-bit): 4.6.5-253511702, revision: github-musescore-musescore-653f38d
Regression
I was unable to check
Operating system
macOS 13.6.3
Additional context
(I feel sure this must have been reported but I couldn't find it.)
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.
Research direction
Reproduce the issue in MuseScore Studio using four bars, many invisible notes in the first bar, and Show invisible turned off. Start by investigating the engraving and bar-width layout path; compare the first bar with the other three and verify that invisible notes no longer affect its width while the layout stretch setting remains respected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100