LOL! Yes, that is a good point about map projects that end. You never
know when someone will turn over a rock and find 20km of cave.
I tried using a sequence of select and unselect directives, but it
appeared as if the unselects were ignored and only the last select was
actually used. I asked a question a few weeks ago about the scope of
select, but never got an answer. As near as I can figure, the scope of
select is the entire thconfig file regardless of where select appears.
Some years ago I created a shell script to string together calls to
therion with different thconfig files. It worked and was a bit of a
bother to maintain. With my current project I use a system call in
thconfig.
I agree about projected elevations not being all that useful. It turns
out I had confused "elevation" and "extended". What I really want is
"extended". It was an easy change to redefine the scraps and the export
command.
===============
Bill Gee
On 2/13/25 13:39, Bruce Mutton wrote:
Kia ora!
You mentioned constant fiddling with the {x}{y}{anchor} parameters as the
map changes. That is the reason I save photos and profiles for the very end
of a cartography project.
You have projects that have an end?
A thconfig file can have exactly ONE "select" directive.
Um, I think there is plenty of flexibility with select and thconfig usage.
For almost all of my projects I manage one thconfig and multiple select
statements within that (perhaps you are counting these select collections as
'one'). Admittedly I usually amalgamate map definitions to reduce these to
a single select requirement per projection per run just for convenience.
But multiple selects per projection work just fine, at least they did a few
versions ago.
And selects for each projection in a single thconfig per run are my norm. ie
select mapPlan
select mapExtended
select mapProjection256 (I don't tend to use projected elevations these days
- none of my caves are straight)
select mapProjection135 etc
There is also the possibility to use indexes to manage multiple variants of
a single projection in a single thconfig*.
select mapPlan
select mapPlan:Enlargement
* It might be possible to change the projection of plan maps to
plan:enlargement on the fly with revise, but I haven't actually pulled this
off. Were I try to this, I would currently draw the enlarged passage a
second time (tracing over the original drawing, possibly in the same th2,
but with an index added to the projection), but that is a bit of a hack.
But as Tarquin mentioned, it is not possible to export based on one
projection's set of selects and then choose another set of selects for that
projection in the same thconfig run (The existence of unselect suggests
this might be possible, but I have not had any luck with it and while some
have talked of it, I don't recall an example where unselect has been used
successfully for any purpose).
This is a case where multiple thconfigs can be used with a script to wrap
them all together as Tarquin describes.
I have chosen a simpler, limited approach without automation and manage a
single thconfig, manually commenting and uncommenting lines to get bespoke
outputs on a run by run basis.
Either approach seems to be fine, and what works best likely depends on
preference and objectives.
Bruce
_______________________________________________
Therion mailing list
[email protected]
https://mailman.speleo.sk/listinfo/therion
_______________________________________________
Therion mailing list
[email protected]
https://mailman.speleo.sk/listinfo/therion
