.. we only plot a sparkline for activities in the last 14 days
and don't plot zero values.
.. alongside the sparkline the max and min are shown to provide
context as the Y-axis is scaled to the data
.. not quite working right - need to look at how
the axis range can be set after the data has been
modified as it seems to break things.
.. looks back 21 rides, but perhaps would be better to
look back n days.
.. when looking for activities it doesn't filter so
you see zero values for other sports e.g. power
will be zero for a swim
.. needs refinement after real users get to try it
.. not really a memory leak, more a design flaw in
the way QParallelAnimation works (it assumes you
don't reuse it).
.. there may be other issues with the other animation
groups but can look at those separately.
... Default directory for the WebEngine Profile and Cache is /AppData/Local/<AppName which is the same GC uses as Default for Athletes
Changing the location for QtWebEngine needs to be done for EVERY QWebPage. Until the use of QtWebEngine is limited to a few locations
the easier way is to filter out the Directories created by QtWebEngine (assuming that no-one will call their athletes either "cache" or "QtWebEngine".
... This is only done if build with QtWebEngine and for Windows (on other OS Qt uses a better location for cache data, not a user location).
.. enforce use of QT 5.8 for building the Overview and
use of Qt Charts.
.. Qt 5.7.x doesn't neccessarily come with Qt Charts as it
was a technology preview (and breaks the current Appveyor
builds)
.. hacked in a proof of concept, using Qt Charts
.. only does the time in zone for HR at present, but can now
look to refactor to better code and then add in pace, power
and w'bal time in zone too.
.. note that now we are using Qt Charts the overview will
only be built with Qt >= 5.7
.. although hacked in, at least we get a dashboard that looks
like the real thing (till we have configuration code).
.. need to work on adding time in zones via Qt Charts next !
.. modes for config and view scrapped - too confusing when you
have config of layout vs config of individual cards
.. need to set a constraint on the size of each card to make
it easier to design content and manage typefaces in a
consistent manner across the cards
.. add / delete / modify will be made available at all times.
add will need a '+' card to float at the end of the
dashboard, whilst delete and modify can be on the card
decoration.
.. using a gear icon in the top right to switch between
viewing an overview and configuring it.
.. now need to think about how cards react and are
decorated and the main mechanisms for configuring
the content on the page (not the layout).
