<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)"><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;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@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><span style='mso-fareast-language:EN-US'>Hi Marco<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>I am not sure I understand, let me test my thinking, for everyone to pick apart :)<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>I think the extend options provide control of the non-splay survey legs. In general that control amounts to left, right, vertical, not at all, or not visible.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>The splay legs should just ‘wobble around’ as a second order effect, in response to the extend parameters applied to the non-splay legs.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>So the only sensible behaviour for splays is ‘extend auto’, and my observation is that this is already coded into PocketTopo and Therion, and so there is no reason to require the user to invoke ‘extend auto’ manually.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>As noted in previous threads, Therion and PocketTopo do manage to orient splay legs differently. Quite often I have to mentally reorient splays when drawing in Therion Drawing Editor. Neither application seems to do it perfectly, but then because the shape of the extended centreline network is as much an arbitrary artistic choice on the part of the user, as it is based on hard numeric data, there is perhaps no ‘right approach’ for the software to take. I suspect that I have observed that TopParser can affect the orientation of splays as well, but I am not sure of that.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>I think the right approach is to aim for Therion (and PocketTopo, TopoDroid) to orient splays automatically, based on the extend directions of the incoming and outgoing non-splay legs. If the applications were to allow direct user control of splay extend direction, then the statements should not be able to be confused with existing statements that control the non-splay legs (ie adopt extend splay left, extend splay right, extend splay vertical, extend splay auto). Perhaps this topic is something the authors should collaborate on to achieve a consistent behaviour?<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>What do you think?<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Bruce<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><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>Marco Corvi via Therion<br><b>Sent:</b> Thursday, 7 June 2018 11:29 PM<br><b>To:</b> therion@speleo.sk<br><b>Cc:</b> Marco Corvi <marco.corvi@gmail.com><br><b>Subject:</b> Re: [Therion] Conflict between "extend ignore" command and inverse legs<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Arial",sans-serif'><br><br>I have commented all the splays "extend ignore", and Therion is doing <br>now a good job, ignoring the appropriate leg (extend ignore 83 92). All <br>the splays "extend ignore" was confusing the Therion compiler.<br><br>This data is an export from Topodroid, that incorporates the "extend <br>ignore" command before the splays shots. I will comment to Marco Corvi <br>on the problem.</span><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Arial",sans-serif'>@ Evaristo & Bruce:</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Arial",sans-serif'>what about a command "extend auto", which means let therion decide how to extend the splay shot ?</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Arial",sans-serif'>for the moment therion parser could behave as if the command weren't there.</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-size:9.5pt;font-family:"Arial",sans-serif'>marco</span><o:p></o:p></p></div></div></div></body></html>