Hi Bruce,

I have fixed the altitude coloring in latest commit, but I was not able to
reproduce your strange coloring of scraps. For me it seems to work fine.

Could you please send me some data sample for inspection of this bug?

Thanks, S.

On 9 December 2017 at 04:52, Bruce Mutton via Therion <[email protected]>
wrote:

> Stacho
>
> FYI not only are the colours inverted, but they are a bit out of order as
> well.
>
> Refer the images.
>
>
>
> I have not used any lookup syntax yet, partly as I am keeping my projects
> compatible with earlier Therion versions.
>
> These were generated with 5.4.1+ce29e7b
>
>
>
> Bruce
>
>
>
>
>
>
>
>
>
> *From:* Therion [mailto:[email protected]] *On Behalf Of *Stacho
> Mudrak via Therion
> *Sent:* Thursday, 9 November 2017 11:54 PM
> *To:* List for Therion users <[email protected]>
> *Cc:* Stacho Mudrak <[email protected]>
> *Subject:* Re: [Therion] Development 5.4.1+4369eea inverts and recolours
> altitude legend
>
>
>
> Hi Bruce,
>
>
>
> thanks for pointing out this bug. I will check the order of numbers, I
> have probably made some mistake when dealing with automatic color scale
> generation.
>
>
>
> I have rewritten the scale code completely, but I had no time until now to
> write the docs. But if you want to try, something like that should now work
> in the layout:
>
>
>
> lookup altitude -title "Altitude legend"
>
> 700 [100 0 0] "700 m a.s.l."
>
> 680
>
> 660
>
> 640
>
> 620
>
> 600 [0 0 100] "below 600 m"
>
> endlookup
>
>
>
> It should generate red -> blue scale with desired values. Also explo-date,
> topo-date should now work with addition to maps, scraps. E.g.
>
>
>
> export map -layout-color map-fp topo-date
>
>
>
> and for example:
>
>
>
> lookup topo-date
>
> 2010.12.31 [] "2010 and before"
>
> 2011.12.31 [] 2011
>
> 2012.12.31 [] 2012
>
> - [] "2013 and later"
>
> endlookup
>
>
>
> You may specify multiple lookup tables for same criterion using ":"
> separator in label
>
>
>
> lookup altitude:scale1
>
> 600
>
> 800
>
> endlookup
>
>
>
> and
>
>
>
> lookup altitude:scale2
>
> 800
>
> 750
>
> 700
>
> endlookup
>
>
>
> and use then "color map-fg altitude:scale1" or "color map-fg
> altitude:scale2"
>
>
>
> You may use also:
>
>
>
> lookup maps
>
> map1@some_survey [color]
>
> map2 [color]
>
> map3 [color]
>
> endlookup
>
>
>
> Same should work with scraps. With maps, also more simple way should work
> - you may specify color of a particular map within selection.
>
>
>
> select map1 -color [100 0 0]
>
>
>
> Also intervals should work:
>
>
>
> lookup altitude
>
> [1500 1600] [] "cave floor 1"
>
> [1800 1900] [] "cave floor 2"
>
> endlookup
>
>
>
> If you are willing to try, I would appreciate any feedback. Probably there
> are a lot of bugs because a lot of use-cases. I was not able to test them
> all.
>
>
>
> S.
>
>
>
> On 2 November 2017 at 10:05, Bruce Mutton via Therion <[email protected]>
> wrote:
>
> I’ve just noticed that the latest development snapshot 5.4.1+4369eea seems
> to have messed with the altitude legend.
>
> You can see from the screenshot below, which shows part of identical
> project compilations, one with 9d96803 and then one with 4369eea.
>
> Pretty sure I have not made any other changes that could have caused this
> at my end, and I see that some of the intervening commits on github relate
> to colour changes.
>
>
>
> Neutral (perhaps) changes are that there are more colour bands and the
> colours are brighter, in the legend at least, though not in the map.
>
> A negative change is that the altitude range is now upside down.
>
>
>
> Bruce
>
>
>
>
> _______________________________________________
> Therion mailing list
> [email protected]
> https://mailman.speleo.sk/listinfo/therion
>
>
>
> _______________________________________________
> Therion mailing list
> [email protected]
> https://mailman.speleo.sk/listinfo/therion
>
>
_______________________________________________
Therion mailing list
[email protected]
https://mailman.speleo.sk/listinfo/therion

Reply via email to