This object is in archive!
Where is the difference of the dashboard charts ?
Answered
We have 2 Dahsboard charts per data source and I don't know which chart does what.
Change language does not work on my phone (maybe my config is broken, does not matter), which means I have to provide the german names, Maybe it's only an issue of the german translation?
Trackrecording:
Diagramm (1)
Diagramm (2)
Navigation:
Diagramm (1)
Diagramm (2)
Does anybody know the difference between Chart 1 and Chart 2? Because they look the same for me but maybe I havn't enogh sensors connected to get any difference.
I did have trouble to find any information about them. Maybe it would help people alot if we could get a better chart name. And if this is a translation error, a good english name would be better then a generic translation.
The same question
It is not about "same chart". In detail of chart you may set what you want to see on it. So imagine you may now place into dashboard two charts for track recording, where one will display altitude/distance and second speed/distance. Anyway, agree that it should be made better with some autogenerated ID on the background.
It is not about "same chart". In detail of chart you may set what you want to see on it. So imagine you may now place into dashboard two charts for track recording, where one will display altitude/distance and second speed/distance. Anyway, agree that it should be made better with some autogenerated ID on the background.
Hello Falco,
there is generally no difference. Hmm ... its purpose is made by a developer so :) ... every item in the dashboard needs to have its unique ID, so I added an option to place two charts into UI, where both has unique/different identification. That's why all have the same names just with a number. Clear?
Hello Falco,
there is generally no difference. Hmm ... its purpose is made by a developer so :) ... every item in the dashboard needs to have its unique ID, so I added an option to place two charts into UI, where both has unique/different identification. That's why all have the same names just with a number. Clear?
That's difficult to document. Your notation is already known as "copy of" name which means I don't know how to improve this to prevent that somebody else would create the same question.
Let's talk about the other way:
Do we need it, I mean, who would like to put the same diagramm twice on a single page dashboard with static layout?
Is this related to an outdated feature where you could create dynamic layouts? For dynamic layouts it make sense to have the same element multiple times in your definition file.
That's difficult to document. Your notation is already known as "copy of" name which means I don't know how to improve this to prevent that somebody else would create the same question.
Let's talk about the other way:
Do we need it, I mean, who would like to put the same diagramm twice on a single page dashboard with static layout?
Is this related to an outdated feature where you could create dynamic layouts? For dynamic layouts it make sense to have the same element multiple times in your definition file.
It is not about "same chart". In detail of chart you may set what you want to see on it. So imagine you may now place into dashboard two charts for track recording, where one will display altitude/distance and second speed/distance. Anyway, agree that it should be made better with some autogenerated ID on the background.
It is not about "same chart". In detail of chart you may set what you want to see on it. So imagine you may now place into dashboard two charts for track recording, where one will display altitude/distance and second speed/distance. Anyway, agree that it should be made better with some autogenerated ID on the background.
I totally forgott this dahsboard customization thing.
i don't like to add to much complexity into the support of display multible element twice.
I totally forgott this dahsboard customization thing.
i don't like to add to much complexity into the support of display multible element twice.
Replies have been locked on this page!