Accidentals on invisible notes are squished

[eakwarren]

Issue type

Engraving bug (incorrect score rendering)

Description with steps to reproduce

1. Create a chord with multiple sharps or flats.
2. Select the chord's bar. In the properties panel, uncheck Visible.
3. Observe accidentals are aligned instead of staggered.
4. Re-check Visible. They return to normal staggered layout.

Supporting files, videos and screenshots

https://github.com/user-attachments/assets/59097d72-f575-468b-a29a-cbd271b5ffb4

What is the latest version of MuseScore Studio where this issue is present?

OS: macOS 15.0, Arch.: arm64, MuseScore Studio version (64-bit): 4.4.3-242971445, revision: github-musescore-musescore-eb6b367

Regression

No.

Operating system

macOS 15

Additional context

Same issue in MuseScore-Studio-Nightly-latest-master-x86_64.dmg | 2024-10-30 03:34 | 152M

Checklist

• [X] This report follows the guidelines for reporting bugs and issues
• [X] I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• [X] I have attached all requested files and information to this report
• [X] I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

[oktophonie]

'By design' in the sense that for many items arranged around notes the usual placement algorithms aren't used when they are invisible, in order to reduce the amount of space they take up and thereby minimise the extent to which they obscure other visible items around them.

[eakwarren]

@oktophonie Respectfully, I think that's poor design. In the invisible chord, how would one tell if there are three sharps or two? It's a usability issue. Also, minimizing the space they take up becomes irrelevant when other staves around them aren't hidden.

[bkunda]

There's perhaps room for improvement here, particularly by way of maintaining the original positions of objects made to be invisible (but obviously without affecting the horizontal spacing). I'd possibly class this then as a feature request.