Closed GoogleCodeExporter closed 9 years ago
It's funny this has never been noticed before. I'll have a look.
Thanks for reporting the bug.
Original comment by gulogulo...@gmail.com
on 22 May 2010 at 2:04
My pleasure.....and thank you for creating such an awesome piece of software. I
hated going back and forth between GTC and ST all the time. Now I can do
everything
in one place with a much better interface.
Original comment by nemesisr6@gmail.com
on 22 May 2010 at 4:38
You're welcome.
I checked otu quickly on my PC and wasn't able to reproduce the problem you
mention. Do you get this all the time? Is it for all types of target (I think
I
tried speed)? If yo uget it all the time, sending me your logbook would help
me
debug this problem.
Thanks
Original comment by gulogulo...@gmail.com
on 24 May 2010 at 1:22
So far I get the problem all the time. However, it is only for the speed
target that
it occurs. It does not happen for cadence, heart rate or power.
I have attached my logbook to hopefully help with diagnosis.
Original comment by nemesisr6@gmail.com
on 26 May 2010 at 10:57
Attachments:
Great, I'll have a look when I get a minute. I will report soon.
Original comment by gulogulo...@gmail.com
on 26 May 2010 at 12:28
I had a look and I'm surprised nobody ever pointed this out. Anyways I have a
fix
I'll release in the next version.
Thanks
Original comment by gulogulo...@gmail.com
on 27 May 2010 at 11:44
Excellent. I'm glad to hear it didn't seem like too much of a chore to
diagnose.
Is there any way to get an automatic notification when new versions are
released?
Original comment by nemesisr6@gmail.com
on 27 May 2010 at 1:18
Apart from what's available in SportTracks ("update available" when going in the
plugins page) I don't plan on putting update popups. They personally annoy me
so I'm
not adding them. I'll close this issue when it gets fixed so you'll receive an
e-mail notification I suppose.
Original comment by gulogulo...@gmail.com
on 27 May 2010 at 10:52
Fixed in ST3 version
Original comment by gulogulo...@gmail.com
on 26 Jul 2010 at 12:17
Original issue reported on code.google.com by
nemesisr6@gmail.com
on 21 May 2010 at 7:50Attachments: