Re: Multiple Score Typesetter font sizes

[Richard Shann]

On Sat, 2022-02-05 at 14:27 +0000, Joe and Angela Wilkinson wrote:
> Hi Richard,
> I have a score which needs, say, 3 different Font sizes.
> 13 for the Score, to keep pages down,
> 18 for most parts
> 22 for Guitars which need bigger dots (I'm told).
> It is under development, so needs periodic changes and reprints, and
> it is good when I don't need to remember the size for each Layout.
> You told me how to do this and it works, but is clumsy; for example
>  * Set overall Score Size as 18
>  * Go into Score Properties Editor, find (Print) Set overall Score
> Size and Duplicate it, twice
>  *  * This produces a duplicate but without the Execute command
> button
>  * Go to first duplicate and, using Advanced change the 18 to 33 in 2
> places. 

Did I really suggest this? That is, as it says Advanced and isn't the
best route - sorry! Instead
* Set overall Score Size as 13
* Go into Score Properties Editor, find (Print) Set overall Score
  Size and Duplicate it, ONCE
* Make the duplicate conditional on Only for Default Layout
* Set overall Score Size as 22
* Go into Score Properties Editor, find (Print) Set overall Score
  Size and Duplicate it, ONCE
* Make the duplicate conditional on Only for Guitar
* Set overall Score Size as 18

Now when typesetting anything other than Default Score Layout or Guitar
the size 18 will be used, while the other two sizes will kick in for
those.

> Then make it conditional on Layout: Default Score Layout
>  * Go to second duplicate and, using Advanced change the 18 to 22 in
> 2 places. Then make it conditional on Layout: Guitar
> Perhaps this just IS Advanced in which case OK, but could it be
> possible to have the Execute Command button as well

what you have in mind here is, could these duplicate Directives be
subject to the editing process that executing (Print) Set Overall Score
Size does on the original? They could - the script could look for
duplicates and offer to change any one of them. When I thought about
that I decided that not to go for it at present. Another possibility
would be to offer to make any score size setting conditional and (in
essence) create the duplicate for you if you decide you do want it to
be conditional. That way the user never needs to look at the Score
Properties Editor. But as it stands you need a model in your head of
the score size Directives being stored one after the other with only
the first one being editable via the (Print) Set Overall Score Size
command.

But you shouldn't have to edit the values inside the low-level
directive editor, it's too error prone. Instead edit the default one
via the command and then duplicate & conditionalize it, finally setting
the default one to the value to be used by default.

Richard