FR: Add "work number" token as file name ingredient

Title is fairly self-explanatory.

Now that we have separate flow exports (which is BEAUTIFUL for my workflow and makes me thankful each time I use it), I find myself with a further use case.

Having $n flow number as an ingredient covers many use cases, but for musical theater, where you often have cues that aren’t numbered in exact numerical order (e.g. 9a, 9b, 9c), having the work number automatically populate in the filename would be chef’s kiss.

I could imagine an expanded approach that included more of the text tokens as options within the filename, but of course I don’t know if that’s technically feasible, and I think in practice there are only a select few that I would personally use.

Thanks as always!

3 Likes

Thanks for the feedback. I’ve made a note of this and we’ll see what will be possible in a future version.

1 Like