Well, when I was hacking the anchor watch there was no Route
Manager yet, so waypoints were hard to locate otherwise than by looking at the chart. I wanted to avoid the situation, where there are alarms set, perhaps forgotten, which are hard to see. The secondary reason was the belief that too many alarms lead to excessive complexity of the situation. With the Route
Manager available, this limitation can certainly be relaxed, or perhaps removed, or made a settable .ini value...
The second limitation, 1000 meters max alarm
distance, came from my preliminary experience in testing, showing that with the current
alarm mechanism, alarms centered far away from own ship are not always easy to identify without rezooming (i.e. if the radius of the ragged shape exceeds some value, it is hard to see, what the alarm is, without rezooming and looking around). This may be a personal preference, but I still feel that some limit should be kept here (maybe an .ini parameter again?).
I am at anchor now off La Gomera in the Canaries
, with a single
anchorwatch set at 50 meters...
Next month I will be on firm land again, and I plan to improve perhaps 3 things in anchorwatch:
- allow more watch points (how many are needed? 3? 4? an array of N?)
- allow larger max watch distance (static limit? how big? .ini parameter?)
- if setting the watch on an empty waypoint (distance now would be 0), assume some default value (settable in .ini, or say 50 meters).