Inspector - Time Signature: "Show courtesy“ usability issue

• Jul 11, 2015 - 13:01
S4 - Minor

Steps for reproduction:

  1. Create a score.
  2. Add a line break after one measure.
  3. Change the time signature of the first line to 6/8.
  4. Change the time signature of the second line to 4/4.
  5. Find that a "courtesy" time signature has been added at the end of the first system.
  6. In trying to remove it, select it, open the inspector and find "Time Signature: Show courtesy" checkbox.
  7. Uncheck the checkbox and realise nothing happens.
  8. Search the internet for a possible explanation and stumble upon

Possible solutions I can think of

  • Have the checkbox take effect. (I wonder why it doesn’t but I suppose there is a reason?)
  • Hide the checkbox for courtesy time signatures. (Might still be non-obvious/unintuitive to users they have to select the "real" time signature to remove the courtesy one.)


Status (old) active needs info

The checkbox should be greyed out and is for me in a curreent development build. If you can reproduce this in a nightly build, please post the specific score you are having problems with. There have been some corner cases where the grey-ing out doesn't work properly, but it should work in general and did for me when i tried following your steps. Of course, you lose the line break after step 3, so I added it back. Your screenshot shows notes already entered, so I suspect you managed to hit the corner case from something else you did above and beyond what is listed in your steps. If you find a reliable way to reproduce this,. please post the score and/or full steps.

BTW, from your image, it seems you might prefer to simply disable courtesy time signatures completely in Style / General / Page.

Thanks a lot. You are correct on all points.

I will have to report back with more reliable steps of reproduction for when the grey-ing out doesn’t work.

Status needs info closed
Type Graphical (UI) Functional
Frequency Once
Regression No
Reproducibility Once
Workaround No

Closed due to lack of information. Please report, with precise steps to reproduce, in a new thread if this still troubles you in the latest version (3.3.4).