Not all maps exported in some circumstances
Over the last couple of years I've noticed that I don't always get the maps and surveys I expect to be included in my pdf outputs. At long last I have teased the problem enough to be reasonably sure of it's characteristics. If I don't select any maps or surveys in my th-config file, then as I understood it all the maps in my source files should be exported to pdf. This was the meaning I took from the Therion book descriptions on page 45-46. What I find is that if I have map objects defined that contain scraps AND map objects defined that contain only centrelines (surveys), then the maps that contain only surveys are NOT output unless they are explicitly selected. If the reference to the maps that contain scraps are commented out, then the 'centreline maps' are suddenly output with out being selected. I thought this was contrary to the Therion Book description, and not behaviour that is particularly helpful. If one has gone to the trouble of defining a map with only a centreline or fixed points in it, then one would presumably want it exported when nothing is explicitly selected (which by default should select all). If I didn't want the centreline output, I would not have put it in a map object! To have Therion hide it can only cause confusion I think. So, I think now that I missed the subtlety in the following phrase. "If there is no map selected, all scraps belonging to selected surveys are selected by default for map export " as a map with no scraps is presumably not exported (although in my experience it is if there are ONLY maps with no scraps defined). If this is what is going on, perhaps we could have a new compiler statement like. select all-maps .to amend the current behaviour to select all maps (without having to select them individually) that have being defined regardless of whether they have scraps in them or not. Or perhaps there is already a way to do this? Bruce
select all-maps
what about select the most top map instead of not select anything.
That will only work if you have a top level map. For other than single small caves I have avoided collecting all the maps into a single map, because it makes it more difficult to quickly change the scope or style of outputs directly from the thconfig or index file, and the resulting pdfs are less versatile. Multiple maps means many layered pdfs over which the end user has more control. I do collect together whole caves in larger systems, but, at the top level I tend not to collect more than one cave into any particular map. In addition, there seem to be times when even explicitly declared sub-maps that do not contain scraps or maps (ie contain surveys only) are not included in the output of their parent map. I have not got to the bottom of exactly what conditions cause this however, but it seems very similar to the issue described in my original post. Bruce
participants (2)
-
Bruce -
Martin Sluka