[Therion] therion 5.3.16
+++ Olly Betts [2015-01-07 20:29 +]:
> On Wed, Jan 07, 2015 at 09:11:06AM +, Wookey wrote:
> > +++ Stacho Mudrak [2014-12-30 11:09 +0100]:
> > > * 82-nolang-segfault-fix.patch (this avoids a genuine error case of
> > > language not being defined)
> > >
> > >I believe, this error is already fixed. Are you able to reproduce it
> > > with
> > >current version of therion?
> >
> > I can't remember what the issue was or how to reproduce it. Anyone remember?
>
> No, but thlang_getid() now starts with an explicit check to handle the
> case where the id is -1, so the patch is clearly no longer needed:
>
> const char * thlang_getid(int id) {
> if (id < 0) {
> return "en";
> }
> The important conclusion is that it clearly isn't useful for 5.3.16.
Agreed. That's good enough for me. therion 5.3.16-4 uploaded just now
with the offending patch removed.
Wookey
--
Principal hats: Linaro, Debian, Wookware, ARM
http://wookware.org/
[Therion] Altitude colors range
7. 1. 2015 v 19:41, Bruce : > So what it is looking like, if the contributory maps are all derived from > scraps (or maps in turn derived from scraps), then the altitude range is > correct. > But if there is a map that is centerline derived (ie has no scraps) then the > altitude minima is set to zero. > Only one question: do you have defined entrance? m. -- next part -- An HTML attachment was scrubbed... URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20150107/51ca59f3/attachment.html>
[Therion] therion 5.3.16
On Wed, Jan 07, 2015 at 09:11:06AM +, Wookey wrote:
> +++ Stacho Mudrak [2014-12-30 11:09 +0100]:
> > * 82-nolang-segfault-fix.patch (this avoids a genuine error case of
> > language not being defined)
> >
> >I believe, this error is already fixed. Are you able to reproduce it with
> >current version of therion?
>
> I can't remember what the issue was or how to reproduce it. Anyone remember?
No, but thlang_getid() now starts with an explicit check to handle the
case where the id is -1, so the patch is clearly no longer needed:
const char * thlang_getid(int id) {
if (id < 0) {
return "en";
}
In 5.3.11 (which the patch was created from judging by the paths), this
check isn't present, though it looks to me like thlang_getlang() will
map -1 (which is THLANG_UNKNOWN) to something valid, so it looks to me
like it wasn't actually useful even there.
Perhaps the patch is actually older and was just regenerated for 5.3.11,
but debian/changelog doesn't seem to actually mention it being added,
and the packaging isn't kept in a VCS, so it's harder to check than I
can be bothered to.
The important conclusion is that it clearly isn't useful for 5.3.16.
Cheers,
Olly
[Therion] Altitude colors range
I checked and I can confirm what Bruce is saying. If you don't include centerline in map, the altitude range is correct. If you hide the centerline in the layout (leaving it in the map) the altitude range keeps starting from 0 m. Marco On Wed, Jan 7, 2015 at 2:52 PM, Footleg wrote: > I am not seeing this Bruce. I just tested with 5.3.16. My survey imports > the centreline from a Survex .3d file however, so that might make a > difference? Or maybe I am not understanding what you mean by including the > centreline in the map. I turned off the centreline using 'symbol-hide line > survey'. If I comment that out in my layout then the centreline is drawn in > the map, but my altitude range still covers only the range of my scraps. > > Footleg > > On 5 January 2015 at 22:40, Bruce wrote: > >> OK, the problem is not the previews or the offsets, as it occurs in >> the map examples below regardless of presence of previews or offsets. >> >> What does seem to control whether the altitudes start at zero meters is >> whether the map definition includes a survey centerline. >> >> >> >> If part of map definition includes a survey centerline, then altitudes >> are coloured from zero meters to survey maxima (a bug?). >> >> If map definition has no survey centerline as part of itâs definition, >> then coloured from survey minima to survey maxima (correct behaviour). >> >> >> >> Hence I find this behaviour manifests in maps in progress, but when they >> are finished and I (usually) turn off the centerline maps, they correct >> themselves. >> >> >> >> Bruce >> >> >> -- >> >> *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] >> *On >> Behalf Of *Bruce >> *Sent:* Sunday, 4 January 2015 10:42 a.m. >> *To:* 'List for Therion users' >> *Subject:* Re: [Therion] Altitude colors range >> >> >> >> Hmm, seems like there is an issue here. >> >> Comparing 5.3.10 map with 5.3.16 map as attached. >> >> >> >> Not sure if it might be a side effect of something else, as I think the >> colour range is OK sometimes (I think I noticed some irregularities with >> 5.3.15 but assumed I was imagining things at the time) â maybe the preview >> below triggers it? - I might investigate further if I get time. >> >> >> >> Bruce >> >> >> -- >> >> *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] >> *On >> Behalf Of *Marco Menchise >> *Sent:* Saturday, 3 January 2015 8:45 a.m. >> *To:* List for Therion users >> *Subject:* [Therion] Altitude colors range >> >> >> >> Hello, >> >> I use to color maps by scrap altitude. >> >> >> >> Lately I noticed Therion color gradient starts from 0 m altitude to >> maximum cave altitude. Because caves don't reach 0 m almost all color range >> is unused and most scraps are colored with similar colors. If I remember >> correctly some time ago Therion used all color range because color gradient >> extended from minimum cave altitude (not 0 m) to maximum. >> >> >> >> Am I missing something? Is there a way to use all available colors? >> >> >> >> Thanks, >> >> Marco >> >> ___ >> Therion mailing list >> Therion at speleo.sk >> http://mailman.speleo.sk/mailman/listinfo/therion >> >> > > ___ > Therion mailing list > Therion at speleo.sk > http://mailman.speleo.sk/mailman/listinfo/therion > > -- next part ------ An HTML attachment was scrubbed... URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20150107/f251c14f/attachment.html> -- next part -- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 123853 bytes Desc: not available URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20150107/f251c14f/attachment.jpg> -- next part -- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 123727 bytes Desc: not available URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20150107/f251c14f/attachment-0001.jpg>
[Therion] Compiling Therion projects from Notepad++
Searching for one of my own configuration tips in the wiki, I found it was not there. So I searched my email to find this thread which never made it onto the wiki. I have now updated the wiki with this information (and updated the link to where Notepad++ now lives for downloading it too). http://therion.speleo.sk/wiki/doku.php/contrib:externaleditors#notepad Footleg On 15 January 2013 at 19:41, Bruce wrote: >> I find having multiple thconfig files open so I can compile different > parts of my large cave system project very useful. > > Nice > My usual mode of working is to have many instances of Therion open (a > thconfig or two, and a few .th2, but rarely a .th), each with only a single > file open. All run from the pallet of Therion data files open in Notepad++ > (usually about 10 or many more). > > Your idea is a useful addition to this page > http://therion.speleo.sk/wiki/doku.php/contrib:externaleditors#notepad - > feel free to edit the page. > >>Next I'll see if I can get my batch file to open the output PDF > automatically in Foxit Reader. > > You can probably make use of the file name in your export statement to open > the output file. "Highlight a file and (relative) path and it opens that > file in NP++. Alt + F5, Alt + F6". > > Bruce > > ___ > Therion mailing list > Therion at speleo.sk > http://mailman.speleo.sk/mailman/listinfo/therion
[Therion] Altitude colors range
I am not seeing this Bruce. I just tested with 5.3.16. My survey imports the centreline from a Survex .3d file however, so that might make a difference? Or maybe I am not understanding what you mean by including the centreline in the map. I turned off the centreline using 'symbol-hide line survey'. If I comment that out in my layout then the centreline is drawn in the map, but my altitude range still covers only the range of my scraps. Footleg On 5 January 2015 at 22:40, Bruce wrote: > OK, the problem is not the previews or the offsets, as it occurs in the > map examples below regardless of presence of previews or offsets. > > What does seem to control whether the altitudes start at zero meters is > whether the map definition includes a survey centerline. > > > > If part of map definition includes a survey centerline, then altitudes are > coloured from zero meters to survey maxima (a bug?). > > If map definition has no survey centerline as part of itâs definition, > then coloured from survey minima to survey maxima (correct behaviour). > > > > Hence I find this behaviour manifests in maps in progress, but when they > are finished and I (usually) turn off the centerline maps, they correct > themselves. > > > > Bruce > > > -- > > *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] *On > Behalf Of *Bruce > *Sent:* Sunday, 4 January 2015 10:42 a.m. > *To:* 'List for Therion users' > *Subject:* Re: [Therion] Altitude colors range > > > > Hmm, seems like there is an issue here. > > Comparing 5.3.10 map with 5.3.16 map as attached. > > > > Not sure if it might be a side effect of something else, as I think the > colour range is OK sometimes (I think I noticed some irregularities with > 5.3.15 but assumed I was imagining things at the time) â maybe the preview > below triggers it? - I might investigate further if I get time. > > > > Bruce > > > -- > > *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] *On > Behalf Of *Marco Menchise > *Sent:* Saturday, 3 January 2015 8:45 a.m. > *To:* List for Therion users > *Subject:* [Therion] Altitude colors range > > > > Hello, > > I use to color maps by scrap altitude. > > > > Lately I noticed Therion color gradient starts from 0 m altitude to > maximum cave altitude. Because caves don't reach 0 m almost all color range > is unused and most scraps are colored with similar colors. If I remember > correctly some time ago Therion used all color range because color gradient > extended from minimum cave altitude (not 0 m) to maximum. > > > > Am I missing something? Is there a way to use all available colors? > > > > Thanks, > > Marco > > ___ > Therion mailing list > Therion at speleo.sk > http://mailman.speleo.sk/mailman/listinfo/therion > > -- next part -- An HTML attachment was scrubbed... URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20150107/d0f52d3f/attachment.html> -- next part -- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 123853 bytes Desc: not available URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20150107/d0f52d3f/attachment.jpg> -- next part -- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 123727 bytes Desc: not available URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20150107/d0f52d3f/attachment-0001.jpg>
[Therion] Altitude colors range
If someone is working on this area, then it would be good to allow the minimum and maximum altitude to be used for the colour range to be specified in maps. I currently do this via a hack in my maps, including a scrap containing two artificial fixed survey stations at the min. and max. altitudes I want the map to use for colouring. Provided the rest of the scraps in the map are in this range then the entire map is coloured the same regardless of which scraps I include. So I can generate a map of part of the cave with the same colours as the map of the entire cave. Otherwise maps of small areas of the cave get coloured with very different scrap colours due to the small altitude range of the scraps in the map. Footleg On 5 January 2015 at 22:40, Bruce wrote: > OK, the problem is not the previews or the offsets, as it occurs in the > map examples below regardless of presence of previews or offsets. > > What does seem to control whether the altitudes start at zero meters is > whether the map definition includes a survey centerline. > > > > If part of map definition includes a survey centerline, then altitudes are > coloured from zero meters to survey maxima (a bug?). > > If map definition has no survey centerline as part of itâs definition, > then coloured from survey minima to survey maxima (correct behaviour). > > > > Hence I find this behaviour manifests in maps in progress, but when they > are finished and I (usually) turn off the centerline maps, they correct > themselves. > > > > Bruce > > > -- > > *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] *On > Behalf Of *Bruce > *Sent:* Sunday, 4 January 2015 10:42 a.m. > *To:* 'List for Therion users' > *Subject:* Re: [Therion] Altitude colors range > > > > Hmm, seems like there is an issue here. > > Comparing 5.3.10 map with 5.3.16 map as attached. > > > > Not sure if it might be a side effect of something else, as I think the > colour range is OK sometimes (I think I noticed some irregularities with > 5.3.15 but assumed I was imagining things at the time) â maybe the preview > below triggers it? - I might investigate further if I get time. > > > > Bruce > > > -- > > *From:* therion-bounces at speleo.sk [mailto:therion-bounces at speleo.sk] *On > Behalf Of *Marco Menchise > *Sent:* Saturday, 3 January 2015 8:45 a.m. > *To:* List for Therion users > *Subject:* [Therion] Altitude colors range > > > > Hello, > > I use to color maps by scrap altitude. > > > > Lately I noticed Therion color gradient starts from 0 m altitude to > maximum cave altitude. Because caves don't reach 0 m almost all color range > is unused and most scraps are colored with similar colors. If I remember > correctly some time ago Therion used all color range because color gradient > extended from minimum cave altitude (not 0 m) to maximum. > > > > Am I missing something? Is there a way to use all available colors? > > > > Thanks, > > Marco > > ___ > Therion mailing list > Therion at speleo.sk > http://mailman.speleo.sk/mailman/listinfo/therion > > -- next part -- An HTML attachment was scrubbed... URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20150107/4495f8e0/attachment.html> -- next part -- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 123727 bytes Desc: not available URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20150107/4495f8e0/attachment.jpg> -- next part -- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 123853 bytes Desc: not available URL: <http://mailman.speleo.sk/pipermail/therion/attachments/20150107/4495f8e0/attachment-0001.jpg>
[Therion] therion 5.3.16
+++ Stacho Mudrak [2014-12-30 11:09 +0100]: > * 82-nolang-segfault-fix.patch (this avoids a genuine error case of > language not being defined) > >I believe, this error is already fixed. Are you able to reproduce it with >current version of therion? I can't remember what the issue was or how to reproduce it. Anyone remember? Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/
[Therion] Debian therion using system libproj needs testing
The latest therion debian package (5.3.16-3) uses the system libproj library, not the embedded version included in the therion source (this is good practice for various reasons and should have been done a while ago). Currently the system libproj is 4.8 whilst the therion-inlcuded version is 4.7. These seems compatible for the (farily simple) usage therion makes, but I'd like people who use this to check that it still works the same as before. (I've run it on the cheddar dataset and things still come in in the right place so it appears to work OK :-) Currently in the experimental suite: https://packages.debian.org/source/experimental/therion Wookey -- Principal hats: Linaro, Debian, Wookware, ARM http://wookware.org/
