Acknowledged

Activity Data Control All Messed Up (Eclipse)

If this matters, this is a data field running the latest SDK and the latest Eclipse, simulating an EDGE 1030. Also occurs simulating a Forerunner 955.

===

Bug #1:  If I hit STOP, I can't START the data field again... Start is greyed out. I need to re-launch the data field from scratch.

Bug #2: If I hit PAUSE, it doesn't fire the onTimerPause() function. Does not appear to work.

Bug #3: Once PAUSE is hit, RESUME appears available, but it doesn't do anything. onTimerResume() is not called.

Bug #4: If I hit START before I hit the "play" button (right facing triangle), the simulator appears stuck - no power, no speed, etc.

Bug #5: If I hit LAP it does fire onTimerLap(). But if I hit LAP again, it does nothing.

  • I tested with Eclipse and SDK 4.1.5.

  • Weird. I checked again and added a lap counter and a print statement in my onTimerLap() function. I can hit LAP over and over again, or tap the bottom right watch button all I want. I get the first instance shown in the console. And then nothing. Even killing the Activity Data Control window and starting that again doesn't help.  I know it USED to work. Have you updated Eclipse and are running SDK 4.1.5? I guess I need to make the jump off of Eclipse.

  • Bug #5: If I hit LAP it does fire onTimerLap(). But if I hit LAP again, it does nothing.

    This works for me. Specifically:

    - If the timer is running, I can press the Lap button (in activity data control) any number of times and my data field app reacts appropriately (I have it set up to display the lap count)

    - If the timer is not running, the Lap button (in activity data control) is greyed out, but I can press the "physical" lap button (on the watch in the simulator) and it works once. This is just like the behavior of the real device, where the pause menu gives you the option of setting one lap while the activity is paused.

  • Bug #1:  If I hit STOP, I can't START the data field again... Start is greyed out. I need to re-launch the data field from scratch.

    I agree this is annoying. The workaround is to click on the "physical" start/stop button on the watch in the simulator window.