Hidden notes (in chord) automatically hides all ledger lines but not stems?

[bombasticbobby]

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce

So there are basically two bugs I've found out while using Musescore Studio 4:

1. It's good that glissando can spread staves now, e.g. in piano. However, it does not play in sequence during playback (LH & RH would play simultaneously).

(so, I had a workaround for my midi files, which is to add the entire chord in one hand, with hidden notes instead)

...which leads me to the 2nd bug:

2. When I hide the top notes, it automatically hides the ledger lines, regardless of whether there are notes beneath that need them. Also, it does not hide the extended stem which is very weird...

[see screenshot above, left screen is Musescore interface, right screen is exported PDF]

Hope musescore can fix this soon!

Supporting files, videos and screenshots

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

4.4.3

Regression

No

Operating system

Windows 11

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]

Please file each bug or feature request separately, as it makes it much easier to track them. I'll consider the second one here; for the arpeggio playback issue, please open a fresh issue if you want to.

It is certainly odd that hiding one note should hide all ledger lines on that chord; only those which are required only by that not should disappear. However, this is a duplicate of https://github.com/musescore/MuseScore/issues/14994

Whether or not the stem should disappear or not has been brought up often and is a matter of opinion and context - basically, we need a way to control it for any given situation. That should really be a separate feature request - rather than bug report - if it doesn't already exist.

Also, https://github.com/musescore/MuseScore/issues/15544 will make this sort of workaround (often) unnecessary.