<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-NZ link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Well said Nick. Good advice.<o:p></o:p></p><p class=MsoNormal>Bruce<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Therion <therion-bounces@speleo.sk> <b>On Behalf Of </b>Nick Bairstow<br><b>Sent:</b> Friday, 1 November 2019 23:45<br><b>To:</b> List for Therion users <therion@speleo.sk><br><b>Subject:</b> Re: [Therion] Horrific Warping between maps where I want my lines to join<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>>…<span style='font-size:12.0pt;font-family:"Arial",sans-serif;color:black'> don't join in the middle of a chamber...<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-family:"Arial",sans-serif;mso-fareast-language:EN-US'>I think I said avoid joining in the middle of a chamber as quite often chambers are where you might actually want to use an area fill and I think it is generally accepted that these make joins more difficult. A chamber is usually just a big passage with two walls after all. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-family:"Arial",sans-serif;mso-fareast-language:EN-US'>If there are side passages going off a chamber then its just the same principle, get the end close with a small gap, avoid overlaps and it usually works.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-family:"Arial",sans-serif;mso-fareast-language:EN-US'>I agree with Bruce that joins can with care be usually be considered automatic if fact I can’t remember the last time I used two named line points for a normal passage join. Having two screens helps enormously when getting wall ends close together in different .th2 files.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='font-family:"Arial",sans-serif;mso-fareast-language:EN-US'>As with a lot of things Therion I used to struggle with joins but once I sorted my methodology a problem in this area now is an uncommon event. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>>The only restriction I have found is that there should not be two wide >openings opposite each other in the same scrap. In this scenario the >scrap is ‘broken in half’ and while you will get a nice pdf output, the kml >plan will not plot properly (unless this feature has been fixed recently).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-family:"Arial",sans-serif'>I used to suffer a lot with broken kml outputs, as Bruce says gaps in walls can cause this. I never leave just a gap in a wall, if it is a side passage I put a station shot up it (different number sequence) and then get back to the main passage. In Therion I then draw some walls to the station and always put a wall line across the end, usually -option invisible. The side passage will not then upset the kml output. I find that with the kml output some open passages will work and some will not, not sure why but if you stick a line wall across the end then they all work.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>Nick <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-GB style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US>From:</span></b><span lang=EN-US> Therion [<a href="mailto:therion-bounces@speleo.sk">mailto:therion-bounces@speleo.sk</a>] <b>On Behalf Of </b>Bruce Mutton<br><b>Sent:</b> 31 October 2019 19:07<br><b>To:</b> 'List for Therion users' <<a href="mailto:therion@speleo.sk">therion@speleo.sk</a>><br><b>Subject:</b> [Therion] Horrific Warping between maps where I want my lines to join<o:p></o:p></span></p></div></div><p class=MsoNormal><span lang=EN-GB><o:p> </o:p></span></p><p class=MsoNormal>>…<span style='font-size:12.0pt;font-family:"Arial",sans-serif;color:black'> don't join in the middle of a chamber...<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif;color:black'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>Yes, an interesting thread. As Martin rightly says, joining should not be considered fully automatic, but with care it usually can be, with some provisos. </span><a href="https://therion.speleo.sk/wiki/tips?s%5b%5d=join#joining_scraps_together">https://therion.speleo.sk/wiki/tips?s[]=join#joining_scraps_together</a><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>Joining in the middle of chambers or passages IS perfectly OK, indeed it is necessary every time there is a passage intersection. You just need to ensure that each affected passage has a gap in the wall to accept the join! <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>The only restriction I have found is that there should not be two wide openings opposite each other in the same scrap. In this scenario the scrap is ‘broken in half’ and while you will get a nice pdf output, the kml plan will not plot properly (unless this feature has been fixed recently).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>In Alistair’s example, the pair of green circles indicate a passage opening that can be joined. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>The pair of brown circles show a passage opening on one side and no corresponding opening on the other. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>Hence Therion found the nearest opening it could in the scraps it was instructed to join, and in this particular case was trying to join the three nearest openings together. I predict that an acceptable result would be obtained if a gap were to be opened near the brown circles.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>Bruce<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'><img border=0 width=390 height=408 style='width:4.0625in;height:4.25in' id="Picture_x0020_1" src="cid:image001.png@01D59158.B8CCB270"><o:p></o:p></span></p></div></div></body></html>