Graph in the dashboard

Hi Waldek,

the scaling is determined by the height of the graph cell. If you change its height, the chart line will be steeper. But, then it'll cover a greater part of the screen.

Hi,
first, ask yourself: why do you need such a graph?
For me, the most important thing is the course of the line: will I be going uphill, etc., or downhill?
And if I am at an altitude of 400 m above sea level it would be pointless for the Y axis scale to start from 0 m !? It should, for example, from at least 350 m, then we get an extra line at small intervals, as in the map zoom (X and Y are scaled equally there).
Then we will also fix the problem with the large area for the chart.

Waldek

I'm afraid I don't understand where the problem is... I use the dashboard chart too and it is not scaled from 0 m. It works exactly as you describe:

Hello,

Look at the drawing I have completed with mine.

Point A => is the minimum elevation of the route for the current interval, and point B => is the maximum elevation.

X = value, the smaller the slope will be.

Now notes:

1) The area under the graph (blue) darkens the graph, it is redundant.

2) The line should be able to change its thickness and color.

3) Tapping on the black circle (our current position) should display e.g. the current altitude and slope of the route at this point, it should be in a frame with a white background (better visibility), and after 10 seconds it should disappear.

Now, you can reveal how you managed to get the graph at the top above the navigation. Is it possible to share this dashboard with me (by e-mail)

Waldek

Hi,

I managed to create a similar dashboard, but ...

When it is set on top (also as an overlay) for these 3 visible data bars, the row height cannot be decreased, which makes the map image very small.

To be improved - row height for the described situation.

Waldek

Hi,
I am sending the dashboard version without the graph because there is a problem.
If we use the option - Position: Overlay on the top screen or Inserted at the top, the height of the row is determined by the values of the text of the cell options, while the Edit row and Size options do not affect what any value we enter. Hence the lines in the attached drawing are line height (28) instead of line height 45.
Also, when we put the chart, it in turn causes our row heights to be too large, which we cannot reduce.
So, to correct these errors.
Waldek

Correction
I changed the height of the text to 40. It turns out that the height of the line is independent of the height of the text (it will be "cut off") or of the height specified in the line settings (height set to 45).
I am enclosing a drawing confirming this.
waldek

Thank you for the ideas for improving the chart, nevertheless:

- the axes always display values valid for the whole track even if you display only a crop of the route on it.

- the height of the row and text size are independent values, we don't see a problem with it

- background and line size aren't editable but the color is - see expert settings

We intend to further cultivate the dashboard in the future, there are many other ideas, see https://help.locusmap.eu/search/tag:dashboard.

for https://help.locusmap.eu/attachments/30904?token=59a911a79377e3f2cf3c0bd333b762a4.png
3 lines of dashboard are displayed.
The 1st and 3rd row is set to 40 in height, and the displayed is some 120 minimum !!! ??
You can explain to me why the dashboard does not keep the row height for this case (for the lower layout - it is similar)
I did not get an answer to this question.
waldek

Could you please send the .lb file of the dashboard that makes this problem? You can find it in /Locus/data/dashboard folder. Thanks.

I think the problem is in units of [weight], when using this unit we have the problems that I wrote about.
When all (!) Units match [Size], that's okay.
I can provide screenshots.
For me, [weight] is abstract because its definition is not clear.
This can simplify it all and leave [Size], or it can be in SI units (mm, cm etc.)
Waldek

Hello Waldemar,

explanation of "weight" parameter: app takes available space for the Dashboard, set all rows with fixed height and there will be some remaining space available. And this space is divided into remaining rows based on their weights.

Examle

row1: fixed 100px

row2: weight: 2

row3: weight: 1

row4: fixed 200px

available space: 900px

What happens? row1 + row4 occupy 300px. Remaining 600 is then divided into row2 a row3 by their weights, so row2: 400px, row3: 200px.

Hope this helps understand it better.

Thank you for clarifying the definition of [Libra].
But unfortunately I prefer [Size] for all rows and cells. There is no problem with keeping the row height constant, which, unfortunately, is not the case with [Weight].

waldek

If you prefer the size, then select the size in the number of pixels and set it as you need.