### Issue type UX/Interaction bug (incorrect behaviour) ### Description with steps to reproduce 1. Make a score with two instruments 2. Make a custom part 3. Try to make instruments visible ### Supporting files, videos and screenshots https://github.com/user-attachments/assets/da451a7b-3349-4229-a942-a3830c2dcc72 ### In which versions of MuseScore Studio is this issue present? OS: macOS Tahoe (26.5.1), Arch.: arm64, MuseScore Studio version (64-bit): 5.0.0-260713041, revision: github-musescore-musescore-83bc55b ### Regression Yes, this works in the latest released version and is broken in the nightly builds ### Operating system MacOS Tahoe 26.2 ### Additional context _No response_ ### Checklist - [x] This report follows the [guidelines](https://github.com/musescore/MuseScore/wiki/Reporting-bugs-and-issues) for reporting bugs and issues - [x] I have verified that this issue has not been logged before, by searching the [issue tracker](https://github.com/musescore/MuseScore/issues) 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
Issue type
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
Supporting files, videos and screenshots
video1844280302.mp4
In which versions of MuseScore Studio is this issue present?
OS: macOS Tahoe (26.5.1), Arch.: arm64, MuseScore Studio version (64-bit): 5.0.0-260713041, revision: github-musescore-musescore-83bc55b
Regression
Yes, this works in the latest released version and is broken in the nightly builds
Operating system
MacOS Tahoe 26.2
Additional context
No response
Checklist