turn off Bascamp cache

Former Member over 11 years ago

How can I keep BaseCamp from remembering every track route waypoint and so on, without having to remove them, the routes, track and the lists and maps it makes, manually before I close BaseCamp?
When I start Word, Excel, Publisher, or any other program, only the program is started.
When I open a file, only the file is opened in the corresponding program, not every file I've ever opened with it.
Normal programs open only the file that needs to be opened and not all the files it opened before.
As I make routes, change save them under a new name, do different projects at the same time, and don't want things to be mixed up.
It's quite annoying having to remove all the unwanted things that clutter up the space all the time.
MapSource doesn't have this problem, so is there a switch to keep BS from this behavier?

0 SUSSAMB over 11 years ago

Short answer is no.

0 Former Member over 11 years ago

Unfortunately, that's the way Basecamp was conceived. Apparently their "inspiration" was iTunes, which behaves exactly the same - it opens up with all your music, videos, playlists, etc. But iTunes opens up immediately so it's not much of an issue.

-Boyd

0 BTLAAKE over 11 years ago

Here’s a longer answer. One of the differences between MapSource and BaseCamp is that BaseCamp has a means of organizing objects built into the program. One way to try and draw a parallel between the two programs is:

MapSource: BaseCamp:
computer hard drive ~ My Collection
Windows Folder ~ BaseCamp Folder
MapSource File ~ BaseCamp List

BaseCamp does not create windows folders or files for each list. BaseCamp automatically saves objects as they created. BaseCamp folders and lists restrict what objects are visible a map. My Collection will show all stored objects. A folder will show all objects under that folder and a list all objects on that list.

Lists are not the same as MapSource Files. Each MapSource file can be thought of as a separate “database”. So each file must contain all the information for an object like the waypoint Home. For the users, all those Homes are the same, but for the computer they are all different because they are in separate “databases”.

BaseCamp only allows the access of one database at a time (same as MapSource), but you can only run one instance of BaseCamp (MapSource allows you to open multiple instances of the program). A List in BaseCamp does not contain all the data for an object like Home, it only needs to be able to refer to that object in the “database”. So regardless of how many lists contain Home, there is only one Home object.

This has consequences. One is that any change you make to an object (say a phone number) will appear on all lists that contain that object. If you want to use an existing object as a basis for a new object, it is not enough to send the object to a new list. Once you send the object to a new list you will have to duplicate it. Duplicating will create a new object in the “database” with a new name. Just like MapSource, a “database” (file) can use a name (Home) only once for each object type (waypoint, route etc). You can then remove the original object from the list if you wish (but do not delete it from the database).

Objects like routes, waypoints and tracks don’t take up a lot of space. Custom maps, Birdseye imagery and photos probably do and may affect performance if you have a lot of them (I don’t use them, so I don’t know for sure). I believe you can create more than one database now (or is it just creation of the database in a location of your choosing?). I'm sure someone can chime in on that.

0 Former Member over 11 years ago

For now I've made a workaround by having a batch-file delete the database and the folderdata before BC is opened.
So now I have the choice opening BC with or without remembering the last things I did.
Lets see what the drawbacks are....(besides having only one BC open at the same time, if thats a drawback at all)
Also I discovered some GPI data that BC retrieved from my GPS so I deleted that too, there is no need for BC to remember it.