join two scraps to same end of other srap
I have a passage that splits into two, with the two passages located one directly above the other. I have three scraps that join at the common passage junction. When putting together a plan I try the following; join scrap1 scrap2 #lower end white river (top passage) join scrap1 scrap3 #lower end white river (btm passage) I find that the second join statement is quietly ignored, it has no effect and no warnings nor errors generated. I suspect that I could use the more general point to point join syntax without problem, but, forever looking for the easy way, I'm tempted to ask if there is a valid reason for the above behaviour? Bruce
join scrap1 scrap2 #lower end white river (top passage)
join scrap1 scrap3 #lower end white river (btm passage)
I find that the second join statement is quietly ignored, it has no effect and no warnings nor errors generated.
Well, I do not know why this is the case :( Could you please simplify it and send me some samples that I can reproduce this problem. Of course, join command should not be ignored. Regards, S.
Stacho Here is a stripped down version that illustrates the issue. In the file Late08INDEX.th you can experiment with changing the order and commenting out either of the joins to get different results each time. The second join is always ignored, and no errors reported. (The warnings in this example are due to missing layout files that I have not sent through) Bruce -----Original Message----- From: therion-bounces@speleo.sk [mailto:therion-bounces@speleo.sk] On Behalf Of Stacho Mudrak Sent: Tuesday, 27 January 2009 3:35 a.m. To: List for Therion users Subject: Re: [Therion] join two scraps to same end of other srap
join scrap1 scrap2 #lower end white river (top passage)
join scrap1 scrap3 #lower end white river (btm passage)
I find that the second join statement is quietly ignored, it has no effect and no warnings nor errors generated.
Well, I do not know why this is the case :( Could you please simplify it and send me some samples that I can reproduce this problem. Of course, join command should not be ignored. Regards, S. _______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
Now I know, where the problem is. It is because join commands do not chain. It means join a b join b c does not work :( What works is join a b c where a, b, c are points or lines, but not scraps. It is nowhere written in thbook. It is quite long time in the TODO list to do chaining for join commands, but it was not so urgent yet. So the only way how to solve your join problem, is to name lines or add some invisible points and join these scraps manually - as I did it with your files. Regards, S. It is nowhere written in thbook On Tue, Jan 27, 2009 at 5:57 AM, Bruce Mutton <bruce.mutton@paradise.net.nz> wrote:
Stacho Here is a stripped down version that illustrates the issue. In the file Late08INDEX.th you can experiment with changing the order and commenting out either of the joins to get different results each time.
The second join is always ignored, and no errors reported. (The warnings in this example are due to missing layout files that I have not sent through) Bruce
-----Original Message----- From: therion-bounces@speleo.sk [mailto:therion-bounces@speleo.sk] On Behalf Of Stacho Mudrak Sent: Tuesday, 27 January 2009 3:35 a.m. To: List for Therion users Subject: Re: [Therion] join two scraps to same end of other srap
join scrap1 scrap2 #lower end white river (top passage)
join scrap1 scrap3 #lower end white river (btm passage)
I find that the second join statement is quietly ignored, it has no effect and no warnings nor errors generated.
Well, I do not know why this is the case :( Could you please simplify it and send me some samples that I can reproduce this problem. Of course, join command should not be ignored.
Regards, S. _______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion
It is because join commands do not chain. It means
join a b join b c
does not work :(
What works is
join a b c
where a, b, c are points or lines, but not scraps. It is nowhere written in thbook. It is quite long time in the TODO list to do chaining for join commands, but it was not so urgent yet.
So the only way how to solve your join problem, is to name lines or add some invisible points and join these scraps manually - as I did it with your files.
Thanks Stacho I suspected that might be the case, but just wanted to make sure I wasn't making unnecessary work for myself. Bruce
participants (2)
-
Bruce Mutton -
Stacho Mudrak