.. when a new athlete is created and opened the blankstate page
currently provides options to get data by importing files or
downloading from a device.
.. this update adds the ability to configure a cloud service and
start a sync straight away
.. this UX is introduced since cloud services are now much
more ubiquitous and v3.5 introduced broad support for a wide
range of services.
.. the authorise button on the add cloud wizard now
shows a 'Connect with Strava' icon
.. all other services continue to have a button that
is labelled 'Authorise'
.. this is needed to comply with the Strava API application
guidelines.
.. when data is downloaded from strava we now set the metadata
tag "StravaID" to the id of the activity on Strava.
.. On RideSummary a link is added at the bottom to view the activity
on Strava if the "StravaID" is set.
.. if the user clicks on the link the summary is replaced with the
strava page for the ride:
e.g. https://www.strava.com/activities/962515512
.. this is part of a couple of updates to comply with the Strava
guidelines for consumption of the Strava v3 API, see:
https://developers.strava.com/guidelines/
Some older (Tacx) RLVs do not have a sync point at the end of the course.
This work-around calculates the total distance of the course and sets a final sync point
if one does not already exist.
Revised code in VideoSyncFile::parseTacx to build syncpoint list with correct distances
when speed varies between two points
Revised code in VideoWindow::telemetryUpdate to interpolate position between 2 sync points.
Also do not update video if paused or not running.
Revised code in VideoWindow::startPlayback to set a minimal rate to start if video is
controlled by syncfile. This avoids the initial "rush" that otherwise happened and
makes for a smoother start.
Also reset distance to 0 on start.
As the rlv length now more accurately matches the workout length, we also need a check in
TrainSidebar::guiUpdate that will terminate the workout if the end of the video is reached.
This code has problems when distance is used on x-axis (#2842)
and it is redundant since there is a general mechanism to plot
any XData series as User Data in Activitiy chart.
This reverts commit f095416c5c.
* Initial implementation of Python data processors
* Add RideEditor to PyFIx script editor
* Enable write-access to activity data for python fixes
* Add GC.deleteActivitySample method
* Add GC.deleteSeries method
* Check for python fix for changes before close
* Build python fixes menu dynamically
* Make python fixes first class data processors
* Add GC.postProcess method
* Check GC_WANT_PYTHON and "Enable Python" setting for python fixes
* Add GC.createXDataSeries method
* Clean up ScriptContext ctor mess
* Support editing xdata series
* PDP: Implement xdata append/remove methods
