@balloni55: quite interesting with your track. No matter what I do, I always see only -100/+90 downhill/uphill values. What should I do please, to get third possible values? Thanks ... ah sorry, I've read it once more ... oki, I've downloaded GPX and for my suprise, altitude values in GPX itself are different

.
@Christian: quite complicated task for me ...
one explanation here:
http://help.locusmap.eu/topic/elevation-object-in-dashboardand one more similar topic with my final answer here:
http://help.locusmap.eu/topic/wrong-elevation-gain-during-recording#comment-16777So difference between values during recording and after save should be quite close ... ah same with answer to balloni55, after I read it once more ... we talk about chart from "Add new route", hmmm ... good point, thanks, improved.
Just please keep in mind, that if you draw a track as plain points (lines are not computed for navigation), Locus then interpolate values between points (every 10 m) to correctly display chart and stats. Anyway such points are not saved to database.
@balloni55: problem with dot, funny, thanks
@jajaballard: as @john_percy correctly mentioned. When there is new version compare to test version, then is no need to keep test version as Locus Pro

@john_percy: hmm, you will understand this - seems to be some racing problem between rendering of same place by some old thread (previous draw cycle) and new thread (new tile). I'll be watching this, but it will be really complicated to simulate and fix :/