local time signature issue
MS 3.5.2, Windows 10
When a local time signature is entered that matches the background global time signature (i.e. reverting the local TS back to the global TS), MuseScore enters that TS on all staves in the score even though not desired. The fix is simple (mark all the undesired TSs as invisible) but clumsy and adds to the burden of working with large scores.
In the attached Wagner score, please change View to Show Invisible and notice Page 128.
In measure 546, the violins and violas are changed to a local 2-4 TS for two measures. When changed back to the global 6-8 TS in measure 548 MuseScore implements the change on all staves in the score even though it is only desirable for the violin and viola lines.
Confirming it in the attached Wagner is difficult or impossible once implemented because the error "Tuplets cannot cross barlines" prevents a complete un-do of the process.
Complication- if one creates a simple score from scratch (find attached for your convenience) and changes the local time signature on one stave and then back to the global as mentioned, the problem does not appear.
So maybe it's dependent on the complexity of the larger attached score?
Thanks in advance for your consideration.