[Therion] Surface woes solved but another small question SOLVED

[Bruce Mutton]

To answer my own question, yes, the code inside a thconfig;

   source ./Surface/SurfaceINDEX.th         # terrain image and model

where SurfaceINDEX.th contains the terrain image and model solves the
problem of multiple surface data bloating the output files.

Bruce

-----Original Message-----
From: therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] On Behalf
Of Bruce Mutton
Sent: Thursday, 10 April 2008 7:40 a.m.
To: therion at speleo.sk
Subject: Re: [Therion] Surface woes solved but another small question

...

SURFACE
...

Just a small comment.  I have a hierarchy of 'individual caves' and 'whole
cave system'.  If, in my INDEX.th files, I 'input' the surface.th file
containing the terrain model in both levels of the hierarchy, my pdf and lox
models contain two copies of the surface.  They look and work perfectly, but
I infer this from the increased file size and decrease in speed.

I can not figure out a way to avoid this without manually editing the INDEX
files each time, unless perhaps I can put the 'input' statement referring to
the terrain model in the thconfig files (avoids the multiple references if
it's in the INDEX.th files.  I've yet to try this, but is it likely to work?