Second, this may be a device issue, but I didn't see any place to report device bugs. Since BaseCamp "sees" the issue, I'm reporting it here.
There are really 2 issues, both of which are minor annoyances, not major problems.
Usually I keep the current track recording OFF; only turning it on when I want to record a track. Keep this in mind when reviewing the 2 issues. Both of these issues occur when I plug in my eTrex 20, wait for Windows to recognize it, and then start up BaseCamp to allow it to recognize the unit. Both issues are intermittent, not 100% reproducible.
- BaseCamp shows that there are several Current Tracks on the eTrex 20 with the date/time in the track name, even though tracks were turned OFF (as usual) during those times. They are usually small segments of where the unit has been during that time, of course. But why it should record any current track is a mystery when tracks are turned off entirely.
Several times I've removed the tracks (using BaseCamp) only to find that they reappeared (same name!) later after properly Ejecting the unit and plugging it in, perhaps days later. I'll delete them again, and then they stay deleted.
As mentioned above, this is not 100% reproducible. Some times I can plug in the unit and start BaseCamp and there aren't any annoying Current Tracks. - Again, with tracking turned off, BaseCamp will report an error importing data from the eTrex 20 citing a bad Current Track. I go out onto the device's Garmin/GPX/Current and remove the Current.gpx file to fix the issue; otherwise it will report the same bad track until I remove the offending flie.
This has happened since the last device update. As per the above point, the silly unit shouldn't be recording a current track anyway. But it definitely shouldn't be creating a bad .gpx file! I'm a Software Application Architect, so I could have looked in the bad .gpx file to see if it was malformed XML or mismatched tags or whatever, but I haven't taken the time to do so. I would be happy to submit the bad Current.gpx file to Garmin the next time this issue occurs. Just tell me where to send it. ;)
As both of these have work-arounds, they are not high priority issues (yet). Just thought I'd pass them along since little issues may portend code bugs that can become big issues later on (don't I know!).
