Finally we have found where the problem is, but it will take some time, until we will find clean solution for this bug. It is a behavior of metapost we do not 100% understand yet. Anyway, here is simple metapost hack that you need to add to your layout to fix this bug until we will publish snapshot with clean solution to this problem. code metapost def endfig = scantokens extra_endfig; shipit; endgroup; save ATTR__text; enddef; endcode Best regards, S. On 11/11/08, Stacho Mudrak <s.m@group-s.sk> wrote:
This is strange - it looks like a bug, but I am not able to reproduce it with my dataset - even I have tried various combinations of continuation stations and symbols. I am afraid, I will need your dataset to investigate this problem, or at least output metapost file generated by therion (use therion -d <your-config-file>, it will generate thTMPDIR directory in your working path and there will be data.mp file which I need to check for errors).
Regards, S.
On Tue, Nov 11, 2008 at 11:30 AM, Bruce Mutton <bruce.mutton@paradise.net.nz> wrote:
And to continue a theme, something I noticed with 5.2, and also with 5.2.2
In the picture below, I have defined two continuations with the text "water enters" (the bottom right-most continuations) similar to the following;
point 312.75 -1284.5 continuation -text "water enters" -attr code V -explored 0
The problem is it turns up in continuations defined simply with
point 123.0 456.0 continuation
As you can see there are at least three unwanted instances …
The same thing is going on with the 'tight' continuation text on the left of the picture.
I have attached a continuations list for the whole cave for reference (you can see I haven't started using it properly yet, but I hope to in due course)
My mistake or a bug?
Bruce
_______________________________________________ Therion mailing list Therion@speleo.sk http://mailman.speleo.sk/mailman/listinfo/therion