01.03.2012 14:44, Martin Sluka пишет:

It is a feature, because you may define several maps or submaps so Therion must know which one to export.

IMO, Therion select last defined map if no explicit select. But if select implicit, Therion export map without some parts of it (without title). It's not clear -- WBR, Vasily

01.03.2012 15:09, Bruce пишет:

Remember that if you don't select any maps, by default therion selects all maps, and that if you don't select any surveys, by default therion selects all surveys.

Thanks. I just try to delete main map from project and all sub-maps displayed. My previous message shows my incorrect understanding of Therion. -- WBR, Vasily

...

If you are intentionally selecting multiple maps (so that they may individually be turned on and off in the resulting output pdf),

You may define the maps in "index" file, so you may create as many as you need such layouts with different map subsets and change only the layout index name in source file. In this way you may have allways the "top" map with name of subset.

If I understand correctly, that is a similar approach to what I use to provide a quick useful control to toggle map titles and other features. For a larger cave system that is 'growing' rapidly I am finding that running multiple map INDEXes becomes unwieldy. The authors have to remember to keep them all up to date. (Problem with authors imagination, memory and communication with each other, not the the INDEX approach). A single 'top' map does not however result in a particularly usefully layered pdf file. I like to be able to supply pdf files in which the user can turn on or off each cave, the surface image or the previews as they wish. Particularly where one or more caves are stacked one above the other. Bruce

...

For a larger cave system that is 'growing' rapidly I am finding that running multiple map INDEXes becomes unwieldy. The authors have to remember to keep them all up to date.

Any way you may have partial maps defined and general maps defined from those partial. So the change could be only on one place.

The changes are usually in one place for a single hierarchy (MAPINDEX), but I have started using multiple hierarchies that require duplicate but not quite identical submaps. I am using a tree like structure similar to that (single hierarchy) described on the Mulu pages http://www.mulucaves.org/wordpress/surveying/the-mulu-survey-dataset (but using therion of course). My first hierarchy (MAPINDEX) is for map outputs - these have passages offset where on is above the other. Second hierarchy (MAPINDEX)is for atlas outputs - these use duplicate submaps that do not have offsets (hence my request a while back for a new feature -offsets off, which would avoid the need for this hierarchy) Third hierarchy (MAPINDEX)is for another more detailed atlas output of a particularly complex part of the cave. It mostly uses the same submaps, and always the same scraps, but some submaps are broken up more finely or in different places. Forth hierarchy (MAPINDEX) is for an atlas/map output based around chronology of exploration, rather than geographical location. All of the submaps tend to be different to the above, but as always the same scraps are used. This is reasonably straight forward for a single cave (one level on the hierarchy) but becomes unwieldy for multiple caves and on multiple levels of the hierarchy. Adequately structured, but difficult to remember to update each submap and MAPINDEX as the extent of surveyed and drawn cave grows. As you can guess, keeping the map title under control is the least of my difficulties. I am chasing my therion mantra of 'one input once - many outputs' a bit too hard perhaps (although multiple hierarchies is contrary to that I admit). If I was a bit more clever I could probably condense the first three hierarchies into one, but hierarchies based on other than physical location will always be separate until therion develops a bit more I think. Bruce