BaseCamp - 3 yr. user w/ SUGGESTIONS: & issues:

Former Member over 12 years ago

Running most current version of Basecamp as of 10/15/2013:

1.) SLOW TO LOAD FROM GPS UNIT.....
Being a "techie" familiar with programming languages etc. I find it difficult to believe BaseCamp could/does not provide an "advanced" option setting to select directories on the unit (and chip) to "read" (or ignore) etc.... ~ Now that's a quick fix that could result in "lightening fast" device data reading.

With BirdsEye and other large maps on the external chip, it takes up to 10 minutes to read chip!..... Not too practical when you are just trying to read a few waypoints & tracks etc.....

2.) Basecamp settings measuring distance problem when using MILES:
Meters are great, it shows meters out to 1000 before converting to km.
In feet, not so good. BaseCamp only shows feet out to about 500 feet, and then the measurements turns into tenths of a mile. (not good for distance display) ~ I've resorted to using meters for this reason.....

3.) Minor bug with folder hierarchy: If you move a waypoint from one sub-folder to another, it does not frequently display properly when the parent folder is chosen UNTIL you exit BaseCamp, and re-start it.

0 Former Member over 12 years ago

I will write a case on your folder bug. Thank you for your feedback.

0 Former Member over 12 years ago

Bug: Supporting info...

I will write a case on your folder bug. Thank you for your feedback.

UPDATE RE. BUG:
I don't know what actually causes the relocated waypoint to frequently not appear when viewing from a parent folder in basecamp. (after a waypoint aka "shortcut" has been relocated, copied actually down into a sub folder/list)

One thing I do know is that the waypoint can be created in basecamp. (doesn't need to be captured from gps unit)
I also believe that it has something to do with a new waypoint being initially created and then moved up/down in the folder hierarchy.
(Possibly it's a combination of dragging the waypoint into another folder, and then deleting the original instance!?!?)

Also: One way of addressing this bug (until it is fixed) is to select the sub-folder/list where the waypoint is located & double click the waypoint (like you're going to edit it). If you make no changes, and exit the editing box... The waypoint appears when viewing from the parent folder.

This is a significant UI bug because: Looking at Basecamp at the top parent folder view, you don't know the waypoint even exists/has been created..... (Unless of course, you know it's "there bug missing!") ~ And then you have to go through all the folders to find it (to "double-click" on it to correct the problem).

PS: When using the measuring tool, a right click menu (to move to a different tool, like pointer or hand) would be a slick addition!

~Hope this helps. :D

0 Former Member over 12 years ago

So badly want the measure tool to have user specified increments. Feet, yards, miles...no auto-switching! Same with metric. I thought for certain I was the only one to find this feature lacking. Kudos, TRACKBAK! I have a hard time giving Google too much credit for anything but their "ruler" tool is what Basecamp should emulate. Knowing that the distance of a trail is .3 miles is almost useless to me but knowing that it's almost 530 yards puts it into perspective...for me :)

ETA: I slaughtered your screen name. My apologies, TRAKBAK! :o

0 Former Member over 12 years ago

So badly want the measure tool to have user specified increments. Feet, yards, miles...no auto-switching! Same with metric. I thought for certain I was the only one to find this feature lacking. Kudos, TRACKBAK! I have a hard time giving Google too much credit for anything but their "ruler" tool is what Basecamp should emulate. Knowing that the distance of a trail is .3 miles is almost useless to me but knowing that it's almost 530 yards puts it into perspective...for me :)

ETA: I slaughtered your screen name. My apologies, TRAKBAK! :o

A "quick fix" for this is to switch from yards to metric in settings..... Meters read out to 1000 before "switching over." (And since a meter is only a few inches more than a yard, I find this "acceptable" for my own reference.)

PS: This may be a slight architectural change, but I get very frustrated using the different tools. Unlike google earth (regardless of which tool you are are presently using), whenever you "normal click and drag" (the software senses this): You can move the map. That means, regardless of which tool you're using, you can always "move the map." ~ And "moving the map" is the thing most frequently done for most, regardless of which tool is being used!