On 13/01/2025 10:42, Benedikt Hallinger wrote:
For such cases, I ususally make myself a "build script" that executes the neccessary steps to produce my desired output. in this case it would be some therion commands, and then a final pdfjam one. I would think that adding something "internal" like this could very easily lead to code bloat and feature creep.
I don't really see "add a page break at this point" to be feature creep. We can already combine PDFs internally, but only onto the same page. Having a combined plan, elevation, overview, in the same PDF seems pretty much within scope of Therion - many surveys are produced that way already, but with the restriction that they can only be on one page. Therion also natively creates multi-page PDFs when using atlas mode.
But wasn't there some thconfig command to execute arbitary code after he compile?
Yes, I do that to run wtkhtmltopdf so it is just a Therion .thconfig to run. Run it, it outputs the cavelist, then my wtkhtmltopdf script cleans it up, generates a PDF of the cave coordinates, and then the main plan.thconfig embeds that PDF in the plan survey, so you can see the coordinates.