This is a quite old thing but I am not sure if it is intended, a byproduct of some other feature, or something else.
Let’s say I have a Playing Technique which should be hidden in the score and shown in the relevant part. Let’s also assume that the wrong workflow has been taken and that, accidentally, the PT was Globally hidden in the score.
When working in the part, within Local scope, toggling the Hide property OFF also toggles it in the score. Whatever the reason for this behaviour, the user is left unaware of this happening outside of their eyesight.
I believe that, once one has gone down the wrong way, the only safe way out is to go back in the score, set scope to Local and then unhide > hide again the PT. Is there any other way?
I was also irritated by this more than once! It was in the following similar cases:
- a slurs endpoints are moved in the score in engrave mode; now in the part; when setting the property scope to “local” and unticking the “offset” properties to get a fresh start, this shouldn’t reset the positioning in the score! (but it does)
- setting a tempo to “abbreviated” locally in a part will also set it in the score and in all other parts… I have to go to score and also activate the toggle to be unchecked… (go global for this to correct the parts as well…)
Another strange thing:
2 Likes
With certain local properties, I think particularly those which are just on/off toggles, setting the property globally effectively turns it into a global property – not the same thing as setting it locally in all contexts. You can see this by setting the filter to Global Only after you have set it globally in the score; you might also be able to tell that after you set it globally, the text of the property becomes bold (in addition to being white).
So once you set it globally in the score, it’s now global. When you toggle it off with Local scope in the part, you’re actually not toggling it locally, because it’s not a local property – you’re toggling it globally.
When you toggle the property off (in either layout), it becomes a local property again, and now you can hide it with Local scope in the score layout.
I don’t find this behavior intuitive, and I’ve been tripped up by it more than once.
3 Likes