I think there is a bug or missing feature in the interaction between these two features. Last running I was running outdoors and it happened that iOS terminated Arc Editor in the background. The Arc Editor showed a data gap in the UI, but I thought I could solve this by importing the workout. It did not work very well.
What it seemed to be doing is to keep the original data gap of 25 minutes, and then add the running segments on top. The running segments also had “data gap” due to the watch auto-pausing when I was stopped at a red light.
The first kind of data gap seems solvable. I just needed to go into the individual segments view to split and choose a type. The second kind does not: it remains as a data gap even when I went into the individual segment view to select running.
(Arc Timeline app wasn’t terminated and so it recorded the entire run without needing to import a workout.)
Yeah this is intentional, with the intent being to later add a feature to optionally import the pauses as Visits instead of Data Gaps. But… it’s bad enough UX that I might prioritise getting to that new feature sooner rather than later.
For a recording pause, a data gap is the “technically correct” answer, but not the “what we actually want most of the time” answer. Leading to the messes in your screenshot!
Though that 25 minute data gap still hanging around is … problematic. That does look like a bug. When you go into that one (assuming it’s still around) does the date range of it overlap with the other imported items?
Ah and this is definitely also a bug! That part isn’t by design. I’ve got another task filed for figuring that one out. And possibly will get to that first.
Hm. Well that’s definitely suspect. That’s something that falls into my “should be impossible” zone. Or so my understanding was. But apparently not impossible.
I’ve got a bunch of tasks filed for related things now, so hopefully I’ll shake out the bugs there. Both workout import related and data gap related.
Though I might be lining up to ship v1.0 to the App Store proper next week. So these fixes might get into v1.0.1 instead. But the plan is for the updates to keep coming about weekly still, for a good while longer.
I think I managed to get the overlapping data gap segment gone. I simply use the scissors button to split it, where the first part becomes stationary and the second part becomes running. That seems to do the trick!
