You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Key signature is (in most cases) global property of system. Local key signature for single staff is exception of this general rule.
So it make sense to have master score _keyList property, where global key signatures are stored.
Similar, like we have _timemap and _tempomap.
It would solve some problems, namely:
if first staff has local key signature in place, where global key signature is in score, newly added part copies this local key signature, instead of correct global key signature
wrong-keysig-new-instrument.mp4
if all instruments are removed in Instruments tab, key list for score is lost - newly added instrument has no key signatures (but has time signatures)
missing-keylist.mp4
Problem to be solved
Properly define, what "global key signature is", how it is added to score (standard key signature for all staves), how is removed, ...
Rules should be consistent with time signatures (masterscore._timemap).
Prior art
No response
Additional context
Once this FR would be aplied, #18949 wouldn't be relevant anymore and may be reverted.
Some context - #18906.
The text was updated successfully, but these errors were encountered:
Your idea
Key signature is (in most cases) global property of system. Local key signature for single staff is exception of this general rule.
So it make sense to have master score _keyList property, where global key signatures are stored.
Similar, like we have _timemap and _tempomap.
It would solve some problems, namely:
wrong-keysig-new-instrument.mp4
missing-keylist.mp4
Problem to be solved
Properly define, what "global key signature is", how it is added to score (standard key signature for all staves), how is removed, ...
Rules should be consistent with time signatures (masterscore._timemap).
Prior art
No response
Additional context
Once this FR would be aplied, #18949 wouldn't be relevant anymore and may be reverted.
Some context - #18906.
The text was updated successfully, but these errors were encountered: