Local Time signature not applied when targetted onto the existing time signature

• Nov 18, 2021 - 16:54
Reported version
3.6
Priority
P3 - Low
Type
Ergonomical (UX)
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project

1.) Start with a grand staff score
2.) Ctrl+Drag (Cmd-Drag) a different time signature onto the time signature on one staff.

Expected Result: * The new time signature is applied as a local time signature
*Actual Result:
The new time signature is applied globally

Adding to the confusion is that the highlighted drop target is only the single time signature instance on the target staff; giving the seeming impression that the time signature will be applied as a local one.

Workaround: Add the local time signature by any other method as described in the handbook (drag it within the measure/use Ctrl+click on the measure)


Comments

Interesting, I just discovered this a couple of weeks ago during one of my Café sessions, but I forgot to report it. It's probably been this way forever.

Almost had me convinced the feature just didn't work anymore. I'd love to see this addressed as part of whatever effort is made to clean up the time selection semantics, and/or to actually get local time signatures working better.