The number of "lists" in my collection is getting way out of hand. I would really like to have nested lists that I can expand and collapse like folders, in order to better manage my tracks and waypoints.
Just a word of warning, I ran into this today as I was importing years worth of tracks and routes into BaseCamp. Nested lists, smartlists and folders must have unique names within each type..... If that makes sense. :) You can have a folder named routes, a list named routes and a smartlist named routes but you cannot have a list in each of two folders named routes. I was trying to organize by Year1(Folder) _EventA(Folder) _Routes(List) _Tracks(List) _Waypoints(List) _EventB(Folder) _Routes(List) _Tracks(List) _Waypoints(List) Year2(Folder) etc.
It would be nice to have the list names "alias" under the individual folder rather than have to individually name each one, but this is workable.
I ran into the same constraint but I think I see why this needs to be the case. The database is My Collection. So all List's are indexed at My Collection level. Therefore, each List must have a unique Name to avoid conflicts. This is also necessary when you consider the use of SmartList's since they are filters on the My Collection objects.
Aliasing is used when one creates a Duplicate List. The objects in that List are aliased from the original and are not copies. Significant reduction in database size when this is all you need - for example to create SmartLists.
I'm willing to change my naming convention (a bit) to accommodate this level of data management - and hopefully future enhancements.
