technically, we're not even changing the start time, we're changing the time in the ID tag
Not strictly true, see the excerpt I provided before...
Code: Select all
<Activities>
<Activity Sport="Biking">
<Id>2021-10-21T05:00:13Z</Id>
<Notes>GOTOES Export</Notes>
<Lap StartTime="2021-10-21T05:00:13Z">
<TotalTimeSeconds>2546</TotalTimeSeconds>
<DistanceMeters>26260</DistanceMeters>
<Calories>690</Calories>
<TriggerMethod>Manual</TriggerMethod>
<Track>
<Trackpoint>
<Time>2021-10-21T05:15:00Z</Time>
<DistanceMeters>10</DistanceMeters>
<HeartRateBpm>
<Value>90</Value>
</HeartRateBpm>
<Cadence>67</Cadence>
Note the <Lap StartTime="
2021-10-21T05:00:13Z"> is also updated along with the Id tag. I've made an assumption this is where Garmin/MapMyFitness is getting it's activity start time from but not certain. But for consistency's sake I still think it would be better for the trackpoint times to be shifted to match the lap start time otherwise there's a 15 minute gap between the activity start time and the trackpoint time which is unaccounted for.
Perhaps I'll have the script auto-uncheck if it detects that the user has done a time-shift. That seems like a good idea.
That would certainly have fixed/prevented my issue.
However, I'm not sure if people are doing serial-timeshifts... and uploading to Strava?
I'm doing it because the spinning bikes at my gym don't have a proper clock so all activities start at 31/12/1899 00:00:00. Possibly I'm special in that respect (although they're the specific bikes used for the Les Mills Sprint/RPM virtual sessions so are likely relatively common in gyms across the world). This is actually my sole reason for using your tool, but they do the job perfectly so very grateful for you efforts.
You'd be surprised how challenging it is to meet EVERYONE's needs.
I really wouldn't. I work for one of the UK's largest software providers. I have great sympathy for you
With regard to the "more obvious note on screen" you suggested: Every single feature has a blue Question Mark "?" by it.. and if you click on the "?" the user can get a detailed explanation of what that feature does and how it works. I prefer to use this less obtrusive method than putting a popup message for each feature.
Agree the question mark is there and does explain what's going on if you read it. However the reason I didn't read it was because the label of the field 'Randomize Id tag' seems pretty concise and self explanatory, I woudn't have imagined that it would also shift start times as well without your detailed explanation of how Strava works. So I can see why the question mark might be overlooked for this field. If you're thinking of making it automatically de-select the randomize checkbox when 'timeshift' is selected, then maybe combine this conditional logic with some additional text that appears on screen (i.e. not behind a question mark icon) that says "this option has been deselected because you've picked the timeshift option, see question mark icon for more info..." or something like that?
Don't take any of this as criticism, your tools are providing a lot of value for me personally and I'm very grateful for you efforts. And for you taking the time to respond. Keep up the excellent work.
.