Feature Request - Improved Simulator Activity.Info handling

Hi,

Firstly, the simulator is excellent, so this is much a request to make it better.

I've noticed the Activity.Info in the simulator is populated with the data from the simulated activity or chosen FIT file straight away, which makes complete sense.

However this means it's populated before a Recording is started within an App, and therefore you get a different behavior from the simulator and device. For example you can be miles into an activity on the simulator when it starts recording, where as the device will be on null. It's more exaggerated when you start and stop recording.

I also believe, this is what catches most newbies out on Apps/DataFields, as there are no checks for nulls on Activity.Info in code, as it differs from the device.

Could the Simulator be enhanced to:
- For Apps: Only start populating Activity.Info when a Recording Session is active
- For Data Fields: Have a separate feature to start and stop recording (maybe the Start Button on the Device) from selecting the FIT simulation.

Thanks
Chris

Former Member over 8 years ago

Could the Simulator be enhanced to:
- For Apps: Only start populating Activity.Info when a Recording Session is active
- For Data Fields: Have a separate feature to start and stop recording (maybe the Start Button on the Device) from selecting the FIT simulation.

Have you checked out the 2.1 Beta we released yesterday? It should mostly work the way you describe here now.

chrishares over 8 years ago

Brilliant!

No sorry, I haven't checked 2.1 yet, as I am desperately (and struggling) to get an App update out which is causing real headaches!

Former Member over 8 years ago

I can't guarantee all the null values will match devices exactly, but with the addition of the FIT Contributions feature, we have incorporated the real recording module into the simulator (which was all simulated in the past).

You can now start, stop, and lap the timer while a Data Field is running by using the device keys, or via a menu. Elements like Start Location, Distance, and others will be null until the timer is initially started.