BaseCamp 3.3.0.1 beta posted

This is a preference option. If you'd like it to work the opposite way, check the "Invert scroll while zooming" box under Controls.

Lion inverts scrolls (by default). In this release, we re-invert it back when zooming (to match Control+zooming on Lion). But we give you the option to zoom in the direction you want it to.

Yep, found that this morning - don't know why I missed it last night - age maybe. :o

Cheers,

• Added ability to use a key to temporarily switch to the hand tool. Defaults to the space key.
  

Space Bar does not work - at least not on my MacBook Air (Lion). The other key options, Shift and Command, do work.

Cheers,

My spacebar switches to the hand tool as long as you hold it down. Saves you having to switch back.

Make sure the map part of the window has focus (click once on the map) when testing the various keys. An unfortunate limitation of the OS.

Right you are! Thanks for reminding me.

Cheers,

I'll try to remember to do the drag-n-drop test next. In the meantime, I'm seeing evidence that shaping points may not be fixed, at least when used with a zumo 660.

Attached is a route I created today to test this. I used the route tool exclusively -- no "real" waypoints, just shaping points start to finish. The route draws and seems fine in BC.

When I export it to the zumo, then reboot the GPS and import the route, that also seems OK (though it dismisses the usual import dialog boxes suspiciously fast).

But then if I try to use the route, in the preview map on the zumo it shows a bunch of straight lines that cut across roads -- just as if the route had never been calculated. So I did a recalc and those went away, but so did half the route. Now the magenta line ends at the southern end of the peninsula where Woods Hole is and never continues north of there, as it does in BC. The route in the preview screen shows a checkered flag many miles short of the correct ending point.

Put another way, there are 22 shaping points in this route. They all show up in BC and the route "survives" recalcs just fine. They all make it into the attached GPX file. But in the zumo the route now ends at the 16th waypoint.

-dan

When using the Hide Map Features option and hiding icons, the food and shopping icons don't disappear when checked off. All the other features disappear when checked off.

Other than that, so far, I really like this version of BaseCamp.

I'll try to remember to do the drag-n-drop test next. In the meantime, I'm seeing evidence that shaping points may not be fixed, at least when used with a zumo 660.

Attached is a route I created today to test this. I used the route tool exclusively -- no "real" waypoints, just shaping points start to finish. The route draws and seems fine in BC.

When I export it to the zumo, then reboot the GPS and import the route, that also seems OK (though it dismisses the usual import dialog boxes suspiciously fast).

But then if I try to use the route, in the preview map on the zumo it shows a bunch of straight lines that cut across roads -- just as if the route had never been calculated. So I did a recalc and those went away, but so did half the route. Now the magenta line ends at the southern end of the peninsula where Woods Hole is and never continues north of there, as it does in BC. The route in the preview screen shows a checkered flag many miles short of the correct ending point.

Put another way, there are 22 shaping points in this route. They all show up in BC and the route "survives" recalcs just fine. They all make it into the attached GPX file. But in the zumo the route now ends at the 16th waypoint.

-dan

UPDATE: When I create the same route but use no shaping points, just enough "real" waypoints to force the turns I want, the route behaves just fine on my zumo 660. It imports properly, displays properly, and contains all of the waypoints shown in BC.

So the problem is with shaping points.

Hope this helps.

-dan

Waypoint management is very confusing in the beta.

Example:

I create a waypoint called WH01 in a list called Favorite Routes. I use it in a route. The route appears in that list and in My Collection. The waypoint also appears in both places.

In the previous BC version, if I delete the waypoint, it remains in the route and in My Collection. In the beta, if I delete WH01 it is removed from the route, which recalcs right away, but remains in My Collection.

If I click on the route in My Collection, it is also missing WH01 and has recalced to reflect that change, even though WH01 still exists in the collection.

Routes created in earlier versions of BC which are in the Favorite Routes list work fine, even though their waypoints are not in that list; they reside only in My Collection.

In other words the relationship between lists and the collection has changed and so has deletion of waypoints, and it now makes no sense.

-dan

Perhaps a defect:
- symbols on polygons are flipped on printouts (PDF or printer)
- flipped: turned 180° degrees and mirrored
- see symbols for trees from TOPO Deutschland 2010



Perhaps another defect:
- a small artifact line on cliffs

Regards Klaus

Waypoint management is very confusing in the beta.

Example:

I create a waypoint called WH01 in a list called Favorite Routes. I use it in a route. The route appears in that list and in My Collection. The waypoint also appears in both places.

In the previous BC version, if I delete the waypoint, it remains in the route and in My Collection. In the beta, if I delete WH01 it is removed from the route, which recalcs right away, but remains in My Collection.

If I click on the route in My Collection, it is also missing WH01 and has recalced to reflect that change, even though WH01 still exists in the collection.

Routes created in earlier versions of BC which are in the Favorite Routes list work fine, even though their waypoints are not in that list; they reside only in My Collection.

In other words the relationship between lists and the collection has changed and so has deletion of waypoints, and it now makes no sense.

-dan

This has been the behavior for some time, to my knowledge. I went back and tested 3.2.2 to be sure, and it's the case there, too. It is a bit confusing from some angles, but it was chiefly done so deleting waypoints would behave as expected while looking at a route that contained it.