BaseCamp 3.3.0.2 beta posted

The File menu has that option for the current selection already and has a hotkey (cmd + S). Our context menus are a bit on the crowded side already; is there some functionality that adding this option to the context menu will add for you?

It would just save a step. I almost never go to the file menu or the keyboard for that matter unless forced to so I'm not current on the hot keys. Plus, I'm one of those Luddites who favour the MapSource File approach over the current collection in BaseCamp so I'm constantly exporting lists to .gdb format for use in MapSource.

I should add that I'm a track pad user, rarely a mouse now that BaseCamp supports the "proper" scrolling and zoom functions that the Mac uses. ;)

Thanks for the reply.

BaseCamp supports Custom Waypoint Symbols and various Garmin GPS's support Custom Waypoint Symbols. Aside from the image format (GPS's require BMP no larger than 24x24pix) the only difference is:

BaseCamp writes the GPX as:

<sym> Custom 2 </sym>

and my Montana writes the GPX as:

<sym> 2 </sys>

So, my question is - who's going to change so that Custom Symbols work between BaseCamp and Garmin GPS's?

Cheers,

My understanding of how the mass storage devices (Oregon, Montana, etc.) work is that they write out the filename of the custom symbol in the <sym> key. If you rename the file on the device to "Custom #.bmp" it should work in BaseCamp.

My understanding of how the mass storage devices (Oregon, Montana, etc.) work is that they write out the filename of the custom symbol in the <sym> key. If you rename the file on the device to "Custom #.bmp" it should work in BaseCamp.

Thanks ATHAWK. I did give that a try yesterday and it does work renaming the files on my Montana to "Custom #.bmp". I really don't want to have to do this for all of my customer symbols but since I did in the past I suppose I will.

So, when is BaseCamp going to "play nice" with my Montana and do the Custom Waypoint Management for me so I don't have to keep doing this myself? ;)

Cheers,

More info:

If I attempt to repair the 4GB micro SD card using Disk Utility, it does not report errors but does end up fixing what looks like some stray clusters. So I copied all my data and reformatted the card. Bingo, it shows up just fine in BC. So I transferred a medium-size list to it in BC, no problem, and that list and all its content appears in the lower pane when the SD card is selected.

But quit BC and re-launch and the SD card will no longer load. Endless spinning arrow again.

So once BC 3.3.0.2 "touches" the card, it's toast, at least for use with the beta.

Just to double-check, I then fired up BC 3.2.2 and the card loaded right up no problem.

-dan

On my µSD card in the Montana, I deleted the "userdata.gpx" file before starting BaseCamp. BC starts and recognizes the card as it should. If I transfer and data to the µSD card (userdata.gpx) BC shows the data just fine. Close BC and restart - µSD card is in "eternal transfer" mode again. Close BC delete "userdata.gpx" from µSD card, restart BC, no problem.

This leads me to believe that BaseCamp is not closing the file "userdata.gpx" properly.

Cheers,

On my µSD card in the Montana, I deleted the "userdata.gpx" file before starting BaseCamp. BC starts and recognizes the card as it should. If I transfer and data to the µSD card (userdata.gpx) BC shows the data just fine. Close BC and restart - µSD card is in "eternal transfer" mode again. Close BC delete "userdata.gpx" from µSD card, restart BC, no problem.

This leads me to believe that BaseCamp is not closing the file "userdata.gpx" properly.

Cheers,

You probably missed it further up, but the issue is just with receiving Categories from Removable Media and will be fixed in the next release.

You probably missed it further up, but the issue is just with receiving Categories from Removable Media and will be fixed in the next release.

Yes - I missed. Thanks.

Any progress on KMZ/L Imports? I did notice that if my KMZ/L file only has one Object (Track, waypoint) in it BC will import it. More than one object and no go.

Cheers,

It's working OK for me. Have you tried creating a new category and setting that to straight-line routing?

-dan

It's working OK for me. Have you tried creating a new category and setting that to straight-line routing?

-dan

I believe you mean "Activity" and I was able to switch to Direct Routing but only if I do it before I start editing a route in Along-road style.

There is still a problem switching between Along-road and Direct routing style.

If I start a Route in Along-road style and during edit I change to Direct style, BC does not actually change to Direct routing style. It stays in Along-road routing even when I change the Activity profile to "Direct".

Are you able to switch between Along-road and Direct mode routing while you are creating a Route?

Here is my workflow:

• Select Automotive Activit mode
  
• Select the Route Tool and begin creating a Route.
  
• Select Direct Activity (which should switch routing mode to Direct)
  
• Return to route editing on map. Routing mode is stuck in Along-road mode.
  

If I look at the Routing Preferences when I change to Direct mode this is what I see:



By the way, this condition works in the other direction as well. Activities with Along-road routing style can be "stuck" in Direct style.

I've reinstalled BaseCamp v3.3.0.2 and this is a repeatable condition - for me anyway.

Cheers,

Yes, a new "category" of Activities.

I can indeed switch from Along-Road to Direct while creating a route, but it changes the whole route. In other words, I don't think BC allows you to do part of a route with one activity set, then do another portion using another activity.

Also, when I make the switch, it is NOT reflected in preferences (which actually is logical if you think about it). But I can tell it worked because the route on the map changes dramatically.

-dan

Interesting that my v3.3.0.2 code is behaving different than yours/others. I've downloaded a "fresh" install each time I think it is not behaving.

The Preferences should indicate conditions set by the user. In this case, the Activity "Direct" is corrupted and is not reflecting (allowing) conditions to be set by the user (me).

The screen shot I post above is a repeatable failure of the "Direct" Profile being stuck in Automotive routing style. Once it is corrupted it will not go back to Direct. I can create a new Activity and use the Direct routing style but. . .

Yeah, I am painfully aware that BC does not support creating a mixed-routing-style Route. But why not? MapSource did and that allowed us to deal with crappy data in routable maps along with the benefit of routing Info on the GPS.

We use to do this stuff all of the time between MapSource and the older GPSMAP Garmin devices - they would not recalculate a Route upon import - unlike most of the newer GPS's. This provided us with the benefits of Routing info on the GPS and the ability to travel in areas of our maps that didn't have any/correct road data.

There are a few benefits of using BC over MapSource, but I must say, I could not recommend to anyone using MapSource that they should change if they rely upon the features mentioned above.

It's really quite interesting how with "old" software we can do so much that the "new" software can't seem to come to grips with (both BC and GPS units). I know of no Garmin customers that like the idea of moving backwards in capability. :confused:

Cheers,

P.S. Please excuse my frustration...