Play selector in Propertie not present in parts

[Gai-Luron]

Issue type

UI bug

Bug description

Play selector not present in properties in part when selecting note.

Steps to reproduce

Create score with 2 part. Open part ans select note. Go to properties, no Play selector exist

Screenshots/Screen recordings

Conductor

Part

MuseScore Version

MuseScore version (64-bit): 4.2.0-232980304, revision: github-musescore-musescore-30a7714

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

OS: Windows 10 Version 2009 or later, Arch.: x86_64,

Additional context

No response

[cbjeukendrup]

I seem to recall that this is by design, but you're not the first who is confused by it / thinks it's a bug, and actually I don't see a very good reason to hide this property in part scores. However, I do think it should be a "global" property, so synced between the main score and all part scores. Playback data is namely only generated based on the main score, because generating it for each part score separately would be a bit wasteful.

[Gai-Luron]

Yes but if you work on one part, it's not easy to find the specified note to mute in main score with 300 Measure and 20 Parts. And yes this property must be global between part and the main score.

[bkunda]

@Tantacrul I too remember finding this interesting a little while back (when designing the parts <--> score feature). Was the "play" checkbox intentionally left out by design (when preparing v.4.0)?

[Tantacrul]

@bkunda - yea, this rings a bell. It was definitely left out intentionally but I'm 90% certain the reason was due to a technical complexity. (Probably edge cases, like 'what happens if I select play in the main score / deselect it in parts?' etc.)

I believe we decided to not have the setting for parts to avoid having to spend time of this complexity - and also because we didn't think it was particularly important leading up to the MS4 release.

[Gai-Luron]

Hello, This is why this setting should be the same for the part and the conductor. Because in the workflow, if we want to modify this parameter in the part, we must switch back to the conductor, search for the measure using Ctrl+F and then go to the correct staff tu unckeck play. When there are 50 measures and 3 staves, it is realistic, when there are 300 measures and 20 staves, it is absurd because it is long and tedious and slows down the workflow enormously. Unless on MuseScore there is the possibility of switching to the correct measure of the conductor starting from the measure of a part.