I did a search for this and only found one topic from 5 years ago with no real replies to it. I’m hoping there’s a better reply available now.
Is there a token available that lets one access the names of the flows entered in the boxes at the bottom of the Setup page? I tried flow1title, flow2title, etc., but they gave me the data from the title fields of the project info for the corresponding flow. I tried flow1name, flow2name, etc., and they gave me nothing. What is available, Steinberg?
Maybe I’m misunderstanding. When my first page template uses flowTitle, if I change the flow “name” in the lower panel in settings, it changes the title in the project info and on the first flow page.
I’m not sure if I’m even doing it right, so maybe you can guide me. I’m working on expanding my Bruckner 6th Symphony transcription for band to include all four movements. For starters, I had “1st Movement” hard-coded into my score and parts next to the name of the piece. Now, though, I’d like to have the movement number be flexible, based on a token.
Make sure the flow title is how you want it to appear in the music, like “1st Movement” – the bit used by flow title tokens is what’s set in Project Info, which might be different than the Flows panel in Setup mode
Show flow headings in the required layouts (if you have local page overrides, those pages can’t be automatically updated to show flow headings when you change this option; you’ll need to remove page overrides to update those pages)
Dorico allows for both a flowName and a flowTitle.
But there is no token for flowName - only {@flowTitle@}.
However on Export Audio, when you specify separate files for flows, Dorico uses the flowName in the filename, not the flowTitle.
Likewise Print /Graphics also gives the option of incorporating the flowName (but NOT flowTitle) .
The way I use this is to give the flowName some short value so the export / Graphics file names are more manageable. The flowTitle which appears on the score can be more descriptive.
Just my 2 cents - suggest we add a token for {@flowName@} would clear up some of the confusion