<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>Bonjour all,</div>
<div> </div>
<div>some months ago Tarquin opened a request on Github to pass point_mapconnection attributes to the actual l_mapconnection (<span class="f1-light color-fg-muted">#434</span>).<br/>
I wonder if something happened there?</div>
<div>As caves don't know how to behave, I have one at the minute that has -just- 5 passages above/underneath each other. Different styled map-connections would make it so much easier to understand the plan and follow the route in the cave (eg make the main ones thicker, change color for overlying/underlying passages).</div>
<div> </div>
<div>has anyone found a way around it?</div>
<div> </div>
<div>cheers,<br/>
Axel</div>
<div> </div>
<div> </div>
<div>from the mailing-list:</div>
<div>-------</div>
<div> Tarquin Wilton-Jones via Therion Thu, 07 Jul 2022 10:04:09 -0700</div>
<div>Hi folks,</div>
<div>I have a challenge, presented to me by some users of one of our surveys.</div>
<div><br/>
We have a cave with layers horribly stacked above each other (10<br/>
passages all crossing the same point!). Simple solution; use map offsets<br/>
to put them all side by side. Use map connection arrows to show what<br/>
connects to what.</div>
<div>That's all good, but they find the default connection arrow hard to see.<br/>
I can redefine l_mapconnection to create my own arrows. Great!</div>
<div>But here's the challenge; they want us to show the difference between an<br/>
unimportant connection, and a major "follow this route" connection. Eg.<br/>
minor ones in grey, major route in red.</div>
<div>I have tried everything I can think of with the mapconnection point: id,<br/>
scale, rotation, -attr etc., but Therion is not creating a<br/>
p_mapconnection. it creates a l_mapconnection, and passes it a path to<br/>
create the line. The attributes are all completely ignored.</div>
<div>Normally, I would use "-attr type major", but that cannot work here,<br/>
because Therion just ignores it. In my opinion, this is a limitation<br/>
that should be fixed.</div>
<div>The only solution I can think of, is to put *two* mapconnection points.<br/>
The l_mapconnection code can then see if the current path matches the<br/>
previous path, and if so, draw it in red. But this is such a horrible<br/>
hack, and prone to failure in future if someone does not realise why<br/>
there are two points, and why they have to follow on from each other.</div>
<div>Can anyone think of a better workaround?</div>
<div>Cheers,</div>
<div>Tarquin<br/>
_______________________________________________<br/>
Therion mailing list<br/>
Therion@speleo.sk<br/>
<a href="https://mailman.speleo.sk/listinfo/therion" target="_blank">https://mailman.speleo.sk/listinfo/therion</a></div>
<div> </div>
<div> </div>
<div> </div></div></body></html>