| Age | Commit message (Collapse) | Author |
|---|
|
we also move the indicator line up in the z stack, as we want the line above the bars. This wasn't obvious before as the elements were all the same colour.
The two processing functions, clamp and interpolateColors are probably not optimally placed in the code. These might move.
|
|
|
|
Steps graph would previously select wrong day on click if there was less than a week of data. This fixes the issue
|
|
|
|
This still isn't ideal, as it only covers the cases where 8h is the smallest division.
|
|
It seems that floats weren't previously supported due to a programming error on my part
|
|
|
|
The weight data collection is manual, so we need a page for the user to input data, hence this commit isn't sufficient for a weight logging implementation on its own.
Weight doesn't have a dataChanged signal in sensorlogd, so that's currently not implemented here either
Because weight tracking isn't for everyone, the preview isn't shown by default.
|
|
- don't bother rendering hours for every label - this isn't useful information and crowds the screen
- make sure we 0-pad any numbers below 10
|
|
This copies a bit of code from https://github.com/AsteroidOS/asteroid-hrm/blob/master/src/main.qml
|
|
|
|
This adds the week graph from the preview page. Tapping on bars allows selecting the day that's currently displayed.
|
|
|
|
|
|
Currently this is a direct clone of the heartrate detail page, and isn't specialised for steps in any way
|
|
This currently just allows viewing heartrate over a day, a week or 3 weeks
|
|
|
|
This was missed when the code was moved from sensorlogd, and caused issues as the bool would arbitrarily be true or false.
|
|
|
|
|
|
Currently the width of the labels isn't dynamic as it was before. This will need fixing.
|
|
The label code has been split into its own set of components:
-TimeLabels: These try to display time labels as best as possible. They can label intervals from a minute to a day, but the code for labelling weeks is still missing. There's also no code protecting against strings overlapping with each other.
- VerticalLabels: The code for these is a bit more 'analogue' than that of the time labels, but it's roughly analogous to previous code.
These have also been implemented for the heartrate graph.
|
|
|
|
|
|
|
|
this splits off the graphs for different sensors into separate files which should make maintenance a bit easier
|
|
settings
UI page is currently empty
|
|
|
|
the move of loggersettings into main is just done so we don't have a duplicate, since we now need it in main.
|
|
|
|
the labels containers are now inset so they actually align with the values (a small offset would be caused by the way that the graph insets its data)
all the code for positioning of the horizontal labels has been redone. This necessitated some changes in the loading code, and a fix to a particularly embarrassing variable duplication.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This fixes an issue where a single bar could fill the entire width of the graph, making a blob shape
This is done by setting an effective minimum of the number of bars that the graph sees, so that an individual bar can't be wider than the width seen when there's three bars
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This app should eventually be a drop-in replacement for that, so it seems appropriate to reuse the colours
|
|
This should mean we always have the most up-to-date data.
I am not sure this will work - the daemon may still be taking the reading as the graph draws, so the data still isn't fresh. Frankly, the daemon's recording mechanism needs a rewrite, and this is a stopgap.
|
|
|
|
|
|
|
|
This page currently only allows enabling/disabling the two currently supported sensors
This also necessitated the addition of a layerstack to allow layer navigation
|
