Hi Bruce,
That explanation makes a lot of sense. It also highlights that really
I want an option to treat any line type as a wall, rather than having
to use one of the limited set of wal sub types. Is there any reason
why I shouldn't be allowed to have a wall that renders like a ceiling
step line in my PDF? This is generally how I have always drawn avens
where some of the wall of the aven is also effectively the passage
wall.
Footleg
On 11 May 2012 22:16, Bruce wrote:
> Footleg (and others)
>
>
>
> Just some musings about how 'wall subtype invisible' and 'wall -visibility
> off' are intended to be used. It seems Footleg is wanting a wall linetype
> that does not exist, and so quite sensibly making his wall invisible in some
> way (so therion knows where the passage interior is), and then overlying his
> wall with the line type he wants (ceiling step, chimney, whatever). Clever.
>
>
>
> Aside from the loch issues my experiences with pdf and kml outputs suggest
> that unless you do this right there will be problems in some cases.
>
>
>
> This is how I think therion might be intended to behave, these are my
> guesses, so please comment if I am wrong.
>
>
>
>
>
> wall:invisible (or âwall subtype invisibleâ is exactly equivalent)
>
>
>
> means 'wall does not exist'. Ie Use this syntax to show that this is the
> boundary of the interior of the passage for this scrap but it is NOT a
> wall. Eg A passage branches off here and there is an open end
> (wall:invisible required if the open end is wider than the passage/scrap
> width) or there is a junction at the end of the scrap where three or more
> passages join, and you need to help therion understand that the âblank
> polygonâ inside the junction is in fact inside the passage, and you donât
> want to (or cannot) use the solution here
> Â http://therion.speleo.sk/wiki/doku.php?id=tbe:wiki3[]=join#joining_scraps
> to fill in the blank.
>
>
>
> Therions scrap âjoinâ statement (default usage) ignores walls with subtype
> invisible (as if they donât exist) and so this is where Footlegs workaround
> for unsupported wall linetypes could come unstuck. Some really odd joins
> could manifest, requiring the user to adopt the more tedious explicitly
> defined line by line joins.
>
>
>
> Therefore if you have a case where there really is a wall, but you want a
> work-around to get a different linetype, then wall â visibility off is
> probably what you should be using.
>
>
>
> Is this an OK explanation?
>
> Bruce
>
>
>
>
>
>
>
>
> ___
> Therion mailing list
> Therion at speleo.sk
> http://mailman.speleo.sk/mailman/listinfo/therion
>