Overview |
About |
Contact |
Requirements |
Download & Install
Screenshots |
Documentation |
License |
Links |
Special thanks to
In this subrange you can define the maximal number of history-items. For example if you set the size to 25 items and add another one the last item in the history will be deleted as well as its map-images (see Picture 7.7).
The change of history-items requires a restart of the application because the change does not affect an update of the history at once. For a proper operation it has to be reinitialized. The next two options in this category define how efficient the cache-algorithm works when you request map-images to reload. If you activate the Looking In History-Cache the loading will first look for a suitable image in the history-cache. However the demanded center has to match exactly the center of a history-map. Otherwise the image will follow the next caching scheme. If you activate the Looking In Loaded Mapset a suitable map will be asked for from the actual loaded mapset. This can result that the demanded track-point is not center of the map-image. In unfavorable cases it might happen that the point is located at the edge of the image.