[Therion] Multiple caves on one map with an offset

[Bruce Mutton]

Good news Bill

A well-earned success.  I had noticed you were likely to run into name conflicts, so glad you figured that out.

 

>Regarding the strange offsets of [0 0 ft] - That is intentional. If I did not do the offset with "above" or "below", then the transparency effects did not work. It was not clear which passage was above or below. They were all mashed together as if they were one layer.

 

It seems like you may have missed part of the recipe.  When defining maps composed of scraps, you need to place the scraps more or less in order of their altitude, with the highest passage at the top of the list.  This in itself makes no difference to how they will render, but in the situation where one overlies another, insert a break statement.  See page 31 of the current Therion Book under ‘map’.

You do not need a break if your map is composed of other maps, because it turns out that Therion inserts an implied break in this situation.  But you still need to sort your map definitions with the overlying maps at the top of the list for this to render as you would want it to.

An as I think you are aware; you need to turn transparency on and set an appropriate opacity value.

 

  transparency on     # see thru passages

  #transparent = 0 <= opacity <= 100 = opaque

  opacity 50         # degree of transparency  

                      #00 = transparent, 100 = block out

                      #40 = subtle, 60 - 70 = apparent: overwritten text still visible

                      #80 = good passage definition but overwritten text barely visible  

 

Still, I had not thought of the approach you have taken.  Maybe darkening up the underlying scraps locally is an interesting style approach to explore (in conjunction with the above).

 

>Does the naming convention of "name at place" extend to more than one layer? Is something like "name at cave@space" possible? Could I write something like AllieMainPlan at AllieSpringCave@BCRPlanMap"?



Of course, as many levels as you like to set up in your project structure, except the syntax is name at place.cave.mastercaves

Only one @, then use dots.

 

One comment I would make, the BigCavernRanch project folder structure is very flat (which is generally a good thing), but now that the Therion data structure is nested (BigCavernRanch includes 4 caves), it might be a good idea to make the folder structure mirror the data structure.  This will make the data structure easier to visualise, and in future make it easier to merge with adjacent cave project data (or split out individual cave projects).

ie folder structure should mirror the data structure;

-BigCavernRanch

                |-AllieSpring

                |-CascadeCaverns

                |-MillCreek

                |-ShiftyRock

And not the current situation in which it is not possible to infer the data structure;

-AllieSpring

-BigCavernRanch

-CascadeCaverns

-MillCreek

-ShiftyRock

 

Bruce

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20191116/50120723/attachment.htm>