Dorico Toggle Button Checkbox combination

[Jayas]

Hi, can somebody explain the use of the Toggle button and the checkbox combination as shown in the video? What does the toggle in both cases actually do? It seems counter intuitive

[pianoleo]

The toggle overrides the global option (Engraving Options > Text > Vertical Position > Use default position) and tells you that the global option has been overridden. The checkbox locally determines whether that particular object should avoid collisions (ignoring the default position) or not avoid collisions (using the default position).

Once the toggle has been set, it doesn’t matter what’s set for the global option; this instance will ignore that global setting.

[dspreadbury]

This has been discussed ad nauseam on the forum, so if you search you’ll find plenty of previous discussions. Here’s just one, which hopefully will provide you with the information you’re looking for:

Do we need all of the on-off switches in properties panel?

Dear Doricorians, Do we need all of the on-off switches in properties panel? Some of them are necessary, but some of them seem to not be required. For example, the on-off switch for the “Border” in the text properties is necessary: [Screen Shot 2020-02-11 at 8.53.16.png] As you see in the example above, there is no on-off switch for “Position”. However, there is an on-off switch for “Placement” in Dynamic properties. I think it can be removed. [Screen Shot 2020-02-11 at 8.53.29.png] I th…

[Jayas]

thank you @pianoleo @dspreadbury. Please understand that searching “toggle button checkbox lower panel” or anything like it did not yield any result. Otherwise I wouldn’t have asked the question. I’ll try harder next time

As you said it is asked many times, I can only think: why is it asked so many times?

I find it really counter intuitive because in this way there are just two elements for one setting.
A tri-state checkbox as a lot of apps are using would be a good option.

Now I know, it won’t be a problem but I’m afraid I’m not the last one to ask the question.

By the way: “ad Nauseum” would be a nice repeat sign for Dorico

anyway the quick responses, as always, are really appreciated!

[pianoleo]

A tri-state checkbox doesn’t tell you what you need to know in this situation, though, which is
a) whether or not the option is respecting the global setting
b) if it isn’t respecting the global option, what’s been set locally.

You (I/whoever) needs to know not only what’s set, but why it’s behaving the way it’s behaving. It’s perfectly possible to set something locally to do the same thing that the current global defaults would do. If you subsequently change the global defaults you need to know why some objects aren’t changing in accordance with the global defaults.

This is the sort of thing that may not strike a casual user as important, but as somebody that often works on projects over months or years with composers and publishers (all separately attacking the file) the transparency is crucial.

[Jayas]

Yes I really do understand the importance of it’s use. My problem was that it felt so counter intuitive. The property for “Border style” seems more logical. Because you override the “Border style” with the toggle button and then set the value to whatever with de dropdown.

I think adding a label to the toggle button for “Align with system start” would help already.

So I’ll put it to rest just wanted to let you know my two cents (and then some I guess)

PS:

the tri-state is actually what is done now but with two input elements

1. Toggle on - checkbox off (manual do not align with system start)
2. Toggle on - checkbox on (manual do not align with system start)
3. Toggle off - checkbox off (use global setting)

this was what I meant for tri-state checkbox in this case: