I've created a much easier process for making alternative typesets for a score (such as a version for a different instrument or a different overall size for the parts). As of version 2.6.6 there are new commands labelled "Conditional Values/Properties" in the Score, Movement and Staff menus which can be invoked to create alternative values for many of the properties you can set on a score-wide, movement-wide or staff-wide basis. I've also updated the manual on the topic of Inclusion Criteria - it now reads:
14 Alternative Typesets From One Score It is common to want to create more than one edition from a single score. The simplest case is Score + set of parts, but you may also wish to have a version of your score transposed for a different instrument, or one containing fingerings for beginners, etc. For this purpose you can make the properties you set on the Score, Movements, Staffs, Notes etc conditional. The easiest way of creating conditional values is by invoking the command “Conditional Values/Properties” from the Score, Movement or Staff/Voices menus once you have created a default value for a property. This command creates conditional versions of the Denemo Directives that dictate the property. For Denemo Directives attached to objects in the music there are menu items to set them conditional. There are two sorts of things a Denemo Directive can be set conditional on, Layouts, and Inclusion Criteria. 14.1 Inclusion Criteria Inclusion Criteria are like flags that you set up or take down in the Print View. So, for example, if you want to generate score and parts for both a transposed and an un-transposed version of your score you can create an inclusion criterion with a name of your choice (say, “transposed”) and set it on the Denemo Directive(s) that control the transposition of the score. The easiest way to do this is first to create the default c->c transposition using the Transpose on Print command and then invoke “Conditional Values/Properties” from the Score Menu to create a different value for when “transposed” is set in the Print View. Then you only have to turn the inclusion criterion on or off in the Print View and the typesetting switches between versions. If the instrument names should change as well then you can use “Conditional Values/Properties” from the Staff Menu to create an instrument name to be used when the “transposed” flag is set. You can create an inclusion criterion in the Print View using the button labelled “No Inclusion Criterion Set” or just create it on the fly when you make a directive conditional using the Conditional Directive commands. For score, movement, staff etc directives you can use the command “Conditional Values/Properties” which lets you make some property you have set have a conditional value in addition to its normal value. For more advaced use you can use Conditional button on the Directive in the respective editor (Score Editor, Movement Editor, Staff Editor etc). For objects (notes, chords, clefs, time signatures, key signatures, standalone Denemo Directives) there is a Conditional button in the Object Editor, or the Make Object Directive Conditional command in the Edit->Object at Cursor menu. Note that if you destroy an Inclusion Criterion then any Denemo Directive that required it becomes effectively unconditional - it will always be active unless you delete it or make it conditional on a layout. The limitation of Inclusion Criteria is that you can only have one active for any one typeset. Making properties conditional on the score layout does not have this limitation. Richard