Ending an activity Edge versus watch

Hi,

Ok, so I've just released quite a fun secondary stopwatch for cycling, it's about as basic as you can get (tap the screen to start timing, tap the screen to stop timing). The guy I built it for seems quite pleased, but he noted that when he does a second activity, it is initially showing the time from the last one.

Now, I haven't got an Edge to test on... I had assumed that it would work like a watch and reload everything when you enter each activity. Obviously, it doesn't...

So... I have two questions and the answer to either one of them would give me a fix!

1. How do I tell that an activity has ended in a DataField? (Allowing me to clear old data.)

2. How do I tell that a new activity has started in a DataField? (Allowing me to initialise new data.)

Thanks,
G

Top Replies

jim_m_58 over 5 years ago in reply to 9635560 +1 verified

or timerTime, or start location or the onTimer* callbacks. There are different ways and some depend on what a DF does.

All Replies

0 9635560 over 5 years ago

I mean... I could just respond to info.timerState changing up from TIMER_STATE_STOPPED, but surely it is possible to be in TIMER_STATE_STOPPED several times on a long cycle if you hit the button at every coffee break?

It doesn't really show a new activity per se.

0 9635560 over 5 years ago in reply to 9635560

I suppose elapsedTime might be the clue.

0 9635560 over 5 years ago in reply to 9635560

Hmm.

Still bothered by this one as I still don't have an Edge to test on.

Data field doesn't reload and I need to wipe the display as it is a calculated value external to the activity that I am displaying.

My latest hunch is that I can base it on Activity.Info.timerState being STOPPED or NOT_STARTED as I presume (even though there is no way to achieve it in the simulator) that might happen on an Edge.

Otherwise, I'm out of ideas.

0 9635560 over 5 years ago in reply to 9635560

Correction. NOT_STARTED, ignore STOPPED as that obviously happens whenever you... ah... stop.

0 jim_m_58 over 5 years ago

elapseTime will stop changing and go back to zero for a new activity.

timerTime will stop when recording stops (a pause will do that), but it too with reset for a new activity.

0 9635560 over 5 years ago in reply to jim_m_58

So, then elapsedTime is the key, I think.

Thanks,

+1 jim_m_58 over 5 years ago in reply to 9635560

or timerTime, or start location or the onTimer* callbacks. There are different ways and some depend on what a DF does.

0 9635560 over 5 years ago in reply to jim_m_58

I can't guarantee there is even GPS, so start location is a non-starter.

But... you get so used to working a certain way, I'd forgotten there even were the onTimer methods... onTimerReset is the man.