replacing time sig for measure that already had a TimeSig will cause no timesig to be visible
This is 3.0 dev bug. Doesn't happen in 2.1dev. And I've discovered that my recent PRs are not the cause of this bug, since this bug occurs on the prior windows 3.0 build fcc5123.
Reproduction steps:
- select meas 1
- double click any time sig (othan than the currently existing 4/4) from workspace or master palette
- observe that no time sig is visible in meas 1 (although note that the measures know that there is a different time sig now, so this is clearly just a visual bug).
- select meas 1 again
- double click yet another time sig from palette
- observe that meas 1 now has a time sig again
- hypothetically keep repeating these steps, and you will see it cycle between showing and not showing
Comments
I shouldn't use the word "adding" because the action of selecting a measure and double clicking a time sig from palette is instead "replacing" the time sig.
I think it's a duplicate, or strongly related, of : #138941: Subsequent time signatures are shown twice when the first one is changed
Since this report, I continue to observe this from time to time, and I find the behavior can evolve according to certain periods and nightlies. But, fundamentally, it no longer works.
Thanks, sounds like a duplicate/strongly related to that.
I'm just glad I didn't screw this up.
Cannot reproduce on current master MuseScoreNightly-2018-03-30-2123-master-b92a6e0.dmg (MacOS):
It got identified as a duplicate of #138941: Subsequent time signatures are shown twice when the first one is changed anyway.
If that isn't reproducible anymore too, let's close that
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.