2020년 11월 25일 (수) | 버전 2.7
Exploiting that a new update has been published since my original review for Lap+ A) now I give 5 stars both for A) and B), because first I realized in the meantime that there is no way to align the data in a better way, moreover the developer was ready for an open-minded discussion about the whole issue. One cannot wish more than an honest and open-minded talk with any service provider.
On the other hand I would like to join the camp of those who would need a copy C) and D) of Lap+. Until now I have used A) for a flat track of 524m and B) for a hilly loop course of 734m, (in both cases using distance based splits), but I fell in love with Lap+ to such an extent that I would like to use its useful 6 data display and split/lap notification even for normal (not loop running) flat and hilly runs with auto lapping after each 1.00 km.
Would it be possible that similarly to App Builder more than 2 copies of Lap+ be available?
2020년 4월 22일 (수) | 버전 2.7
I love this data field and the option of "force backlight on" would make it perfect for indoor activities as well, but I'd need a "Lap+ (C)" or even a "Lap (D)"...
Would that be possible?
2019년 10월 10일 (목) | 버전 2.7
Great datafield! I use it for running-trail running with autosplit and B-version for training intervals with autolap with a slightly different configuration. Thanks for the great work!
2019년 3월 16일 (토) | 버전 2.6.2
I can’t seem to save my personalised settings as each time I set this up and click save I go back in and it’s gone back to the default settings. I really want this to work but it’s just frustrating for now ☹️
2019년 3월 23일 (토), FlowState
Hey Justin, Sorry you're having trouble with the app. I use Lap+ (the other "copy") every day when I run, so I can assure you this isn't expected behaviour. Could you please try changing settings while the *app is not running* (exit your "Run" activity before changing settings.)
If that doesn't work, if you get in touch with me by pressing Contact Developer, then I can gather more information (like which watch you have) and submit a bug report to Garmin, as I'm pretty sure this is a problem on their end. In the future I would appreciate it if you could press Contact Developer first before leaving a negative review, as it gives me a chance to help you. Thanks!