.. implementation of the Veloclinic model, or at least
the first of a few potential models.
.. It may not be correct at this point, but committing
a checkpoint.
.. Added the torque effectiveness and pedal smoothness
data series to the RideFile structures.
.. The only file formats that support it at this stage
are Fit and GoldenCheetah JSON.
.. As more file formats support it we will add it here.
.. The charts/editor now need to be updated to support
these new data series.
.. now has an overlay widget that can contain multiple widgets
and is user movable and resizable etc
.. we show the model derived values for now, but could add other
things at a later date (e.g. MU distribution etc).
Fixes#811.
.. fixup ride mode, interval hover crash/bugs
.. fixup interval compare mode
.. fixup rangemode
NOTE: Compare date ranges is still broken that
will be fixed in part 3.
.. basic ride, bests and model plots all working
.. Compare mode is now BROKEN !
Will fixup the rest tomorrow, needed to checkpoint
the core refactoring work.
.. the CP plot curve is a terrible mess. Mostly from
having multiple significant updates from a number
of notable developers; Sean, Dan, Mark and Damien
have all made significant contributions.
.. But the code contains lots of 'smells' and is very
difficult to follow and update
.. this update makes no functional changes but is put
in place before overhauling the code related to
"calculating" and plotting the different curves.
.. hover curve clear on new ride
.. fix ride plot mode so when plotting ride it always
does. This was fixed by initialising ridePlotMode in
the CpintPlot constructor.
.. Following on from the recent update to add acceleration
this update adds other derived data series based upon the
rate of change.
.. Added to the ride plot and the CP plot.
Not sure of the overall utility of these updates but bear in
mind that they are targetting sprinting and track users and
analysis.
As well as the positive side of this (development of power
cadence etc) we also want to think about and collect data
on fatigue rate (possibly only power and torque)
- fatigue over time
- fatigue over pedal stroke
Basically to distinguish between the four modes
and only show what you are asking for;
* rangemode + normal - the currently highlighted season only
* rangemode + compare - the compare pane seasons only
* ridemode + normal - the current ride and left pane intervals only
* ridemode + compare - the compare pane intervals only
Fixed a few nits that have come to light over the last
few days as lots of new features were developed.
* Fixed interval glitch where first point is zero, caused by
an off by one error in the original code
* Fixed interval creation which also had an off by one error
that mean't 5s curve was only 4s long
* Made the shading under an interval optional, as it is a bit
nasty and was there to hide the glitch in point 1 above
* Made the interval line solid, not dotted, as it looks much
better that way -- especially now its used for compare mode
* Made the title red by implementing isCompare() when in
compare mode.
* Fixed a crash on hover in season compare mode
Fixup all the GC code to use the QWT 6.1 code.
It needed canvas() to be patched to return a
QwtPlotCanvas and not a QWidget.
We could probably get round that with a cast.
When we switch to QWT 6.2 with the multiaxis
support formally baked in we can fix the code
as needed.
Now compiles and links without issues.
Porting the codebase to QT 5 (5.2) to get the
latest bug fixes, performance and improved platform
support.
This first part is to fixup the codebase to compile
on Qt 5, but some aspects have been broken (video).
The second part is to migrate from Qwt 6.0.1 to the
latest Qwt for multiaxis support.
The third part will be to fixup any platform specific
issues or issues identified at runtime.
If you change the plot background to black then the
CP curve is always in black too so becomes invisible.
Added a customisable color for the CP curve and fixed
up a few redraw issues in CP and Ride plot when you
change the colors.
Still need to fixup the other charts, but will do over
time. I suspect almost noone changes the plot colors from
the default values.
.. set to 3600 not 360 (!)
.. updated intervals causing warnings when using values
that were half baked. Now delays recalc() till all
the parameter intervals are set.
