emagin, and others...
Points well taken. It was never intended that users should hand-edit the .ini file. That would be a giant step backwards in UI design....
On the other side, it took me a bit to assimilate the concept
of Coastal Explorer's "Navigation Object". It is clearly the "app operates on document" model, entirely natural for MS developers.
Historical note: I started out with Nobeltec
V4. If anyone has used this before, you know that if you accumulate and keep online a bunch of routes /marks, then the program takes progressively longer and longer to shut down. It seemed to somehow be scrubbing the route list, looking for whatever. After one season's use, the app took 20 minutes(!) to shut down. This was one of the early motivations for opencpn.
opencpn is the way it is because of my personal usage patterns. Routes and marks are dynamic and usually transient. I usually delete today's route as I anchor
. Why? 'Cause I'm where I am, and I know how to get there again if I need to. Tomorrow is another day, route creation is easy (and fun?). My routes usually have two waypoints: Head-pin to head-pin. I don't use tracks. I rarely share routes, preferring to be my own captain
, and assume others want to do the same.
But that's just me.
All that said, I have been known to hand edit the ini file for a quick clean slate....
Anyway, I hear the comments, and solicit more. Maybe we can get some consensus on this and tweak the UI.
As somebody once said:
"Don't sweat it, it's only ones and zeros."