Quote:
Originally Posted by Provist
It would store tracks; but something like one point per hour or less.
|
I would be surprised if that's the case. Version 4.8.8 which I am using stores points at intervals of less than a minute. Has that changed in later versions?
Quote:
Originally Posted by Provist
I know that you can export tracks as GPX. But I wanted to avoid users the hassle to manually export their trace and have to import them again.
|
OpenCPN used to be a nice compact program that would run on almost any old computer. No more. It has fallen victim to feature creep. I don't think it's a good idea to keep adding code to automate things which can already be done quite easily with the existing program. Manually exporting tracks is not much "hassle" and users should be doing that anyway as part of their chart management. If don't export routes, tracks, and waypoints and then delete them you
wind up with an awfully cluttered chart and a program that consumes resources unnecessarily.
Would you want to use a word processing program that retained every document from session to session? Of course not. You create a document in a session. If you anticipate future use for that document you save it. When you need to use it again you open it.
OpenCPN retains everything between sessions unless you explicitly delete it. I believe that was a poor design choice. The workaround is to export routes, tracks, and waypoints to GPX files and delete them from your chart before you end a session. Your next session then starts with a clean chart and you can import only the objects you need for the
current session.
If you take that approach to chart management there is no "hassle" to exporting tracks for use by another program because you will have exported your tracks anyway. All you have to do is point the other program at the track file.
You don't have to tell me mine is a minority point of view. The feature creep I mentioned earlier is clear evidence that the developers are eager to bulk up OpenCPN with additional code and a complex array of plug-ins. I keep reading messages about people who can't load their favorite plug-in because it hasn't been compiled for the latest version of the program. So your request, unnecessary as it is, will probably get a favorable hearing. But while you're waiting for developers to act you might try my chart management technique and see if it doesn't solve a number of problems for you without requiring and developer resources at all.