Suggestion for Folders and Lists

It’s clear from reading posts in this forum that some users keep a lot data. I think it would be a good idea to include the path as part of the unique identifier for folders and lists. I’m not a computer geek, but I’ll try to explain what I mean.

Currently, a unique identifier appears to be type and name. I can have a folder named FALAGAR and a list named FALAGAR, but I can’t have more than one of either with that name.

If the path were part of the unique identifier it would allow organization like:
Trips (folder)/2012 (folder)/Routes (list)
Trips (folder)/2011 (folder)/Routes (list) - two lists named “Routes” within the “Trips” folder.
Wpts (folder)/2012 (folder)/ Southwest (list) – two folders named “2012” in different folders.

If this change is possible, it really should be given a high priority. I hope this makes sense.

0 Former Member over 12 years ago

We have this in the works. If all goes well, this should be in 4.2.

This will indeed only work for lists and folders, for now you will have the unique naming restrictions for waypoints, tracks, routes, etc.

0 Former Member over 12 years ago

Since it's 3 1/2 years since that reply and we're still on 4.1 and not 4.2, could you tell us whether this feature is, indeed, planned for 4.2? If not, would you please put it back on the list of desirable changes? It would seem the embedded folders concept should match that which many of us are familiar with, meaning Windows and Mac.

Thanks.

0 Former Member over 12 years ago

It's been a little more than a month since that reply.

And 4.2 indeed has support for this. The Beta is available: https://forums.garmin.com/showthread.php?36045-BaseCamp-4-2-0-1-Beta-is-available.

0 SUSSAMB over 12 years ago

Just for completeness I've copied my post across from the Mapsource forum where we strayed into BC territory. It ties in with this thread (hopefully) as it discusses folders and lists. We're still missing the functionality that we had only a few versions ago somewhere in the 3.0 series, where importing data from a nuvi we got the nuvi categories showing as lists in BC, like this:

This made it easy to make changes in BC and send everything back, as lists in BC were converted into categories in the nuvi.

Now when we import we just get a long list in alphabetical order:

which is really no good to anyone hoping to use BC to clean up/back up/recategorise nuvi data.

Since the code must have existed it should surely be relatively simple to put it back?