Mac/Windows Software

Basecamp Windows BaseCamp 4.3.0.2 BETA is Now Available

BaseCamp 4.3.0.2 BETA is Now Available

Former Member over 11 years ago

BaseCamp 4.3.0.2 BETA is now available and can be downloaded here:

http://developer.garmin.com/apps/BC/BaseCampBeta_4.3.0.2.exe.zip

You will need to unzip the file before installing.

This release does not support XP.

You do not have to uninstall BaseCamp 4.2.5 and it will not overwrite that installation. The BETA and an official release of BaseCamp will live side-by-side but must be used separately. However the 4.3.0.1 BETA will be replaced.

Below is a list of changes. This is only a BETA release.

Added “Find Intersection” to the Find menu
Added parsing of the primary find text into address search fields
Improved ordering of auto-complete results
Improved street auto-complete results when searching for streets with prefixes and suffixes
Improved some usability issues with address and intersection searching
Improved recovery from corrupted cache information from device maps

Post here if you have questions.

The BETA is currently only for English users.

Before using this release, back up your data.

Please post any bugs you may find here. This release is to assist us in testing with a wider user base and wider set of devices. Bugs may be present, and any feedback is welcomed.

NOTE: We are aware of several issues with address searching on devices. We ask our users to please test this very well and let us know of the issues you find. Some of them will be duplicates of issues we have already found, but the advanced address search is new for this release and we need a good test bed to be sure that the feature is working correctly when we do the full release.

Again, thank you for all who participate.

0 Former Member over 11 years ago

No, if you send me these things this is what I need. Thank you.

0 Former Member over 11 years ago

A few more bugs - I think.

By the way, on your overtype issue, What is your DPI setting? Also if you restart BaseCamp does the problem go away? I am having difficulty recreating the issue.

0 BigLew55 over 11 years ago

Not a bug. By design. This is so that the two waypoints can exist independently such that you can now alter the position of one or the other without affecting the other route.

I can't say that I think that makes sense.

I create a route and then divide it into segments. It doesn't make sense to me to split it at "St Louis Arch" and end up with a duplicate waypoint.

If you see a use case for it, I'd like to suggest the option to keep it one or create a duplicate.

0 Former Member over 11 years ago

Agree

I agree with Bigle55. One is enough no matter how many times that you leave that point. The file just keeps bigger and bigger because of duplicates.

0 SUSSAMB over 11 years ago

Makes sense to me, that way you have two independant routes.

0 Former Member over 11 years ago

By the way, on your overtype issue, What is your DPI setting? Also if you restart BaseCamp does the problem go away? I am having difficulty recreating the issue.

I always use the recommended screen resolution - in my case at the moment, 1920 x 1200.

0 Former Member over 11 years ago

No, if you send me these things this is what I need. Thank you.

Not sure what happened just then but the post I prepared disappeared. So you may get this twice.

I have sent 2 Basecamp routes to the email address you posted and had confirmation of receipt for both ["Automatic Response - BaseCamp (Case 126975)" and "Automatic Response - BaseCamp (Case 126986)"]. If you can't find them, could you post an alternative email address please?

0 BigLew55 over 11 years ago

Makes sense to me, that way you have two independant routes.

Duplicating waypoints never makes sense to me. If I wanted to start from a different point, I would have put a separate point in my route. After thinking about this overnight, I still can't conceive of a reason that I'd want a duplicate such as "St. Louis Arch" and "St. Louis Arch1". It just makes a mess that I have to clean up.

If there is a reasonable case for duplicating this, I'd recommend the option of duplication for the user. Otherwise, if it's not a bug, I'd consider it a design flaw.

0 dpawlyk over 11 years ago

I can't say that I think that makes sense.

I create a route and then divide it into segments. It doesn't make sense to me to split it at "St Louis Arch" and end up with a duplicate waypoint.

If you see a use case for it, I'd like to suggest the option to keep it one or create a duplicate.

The "option" already exists: you can delete the copied waypoint. (You just have to be aware that the waypoint gets copied.)

(There would have to be three options anyway: copy, keep in prior, keep in following. For something that isn't done frequently, it's not clear that adding three more options, in addition to the required delete feature, is that valuable.)

0 BigLew55 over 11 years ago

It would seem to me that the intuitive option when dividing a route would be to have the new 1st leg stop at the point where divided, and the new second leg start at the point where divided. Why would I want to divide a route, and start it at a place where I'm not? That's a completely different route, starting at a completely different place, not a version of the original route now divided to stop in one place (arrive) and begin in the same place (depart).

Creating a duplicate that I then have to delete is just busy work, and busy work in a UI is poor design.

Again, why would you want a duplicate, if your goal is to have a route divided, not create two separate routes? I still can't figure out this logic, or use case?

Consider this as mine:
I recently (last few days), built a multiple day trip from Iowa to Florida to California and back to Iowa.
Using the route tool, I built it all into one route, and added layover and arrival/departure data to applicable points. Since I am on a motorcycle, this includes several gas stops.
Now, to prep the route to load to my GPS, I divide it at hotel stops so that I have a route for each day. After doing this, I have to go in and delete the duplicates, AND correct the start point to EACH leg so that the original waypoint is now the starting point.

And that, folks, is NOT how a UI should treat a user.

Don't get me wrong. This new BETA version has made planning trips fun again, like it used to be in Mapsource. But it still has a bit of progress yet to be made.