David,
I have implemented rollover popups for the display text for Text Points. This is in patch 589 of OD. The documentation is not up to date with this change.

You will find on the 'Display Text' tab of the Text Point properties now has three options for the display of the text: 'Always', 'On Rollover Only' and 'Never'. The defaults for these can be set on the Text Point page of the main properties under 'Options/plugins'.

I have only tested this with the latest version of OCPN and there appears to be a close down issue in this version. It will work with the version that Rick has recently created.

Rick,
I have updated the DR tool, patch 590, so that the right click menu now includes 'Update initial conditions'. This will display the same dialog that you get when you create a DR, but this time it is filled in with the settings you used to create the selected DR. When you click OK the DR effectively gets recreated with the new values. Not quite what you asked for, but I hope a step in the right direction.

Rick,
I have just started the Guard Zone stuff. I have submitted changes to the AIS system to put out JSON messages containing enough information for the Watchdog plugin. I have submitted a change to the Watchdog plugin that will get and process the AIS message and then allow the OD plugin to be checked for an AIS target in a 'Guard Zone'. Currently there is no 'Guard Zone' object, so the check is done, like the anchoralarm, using the Boundary GUID. This is still a work in progress and for the real 'Guard Zones' I will need more information, but we can make a poor man's Guard Zone using the current Boundaries.

I know there are holes in it at the moment as the Watchdog is only going to check every second for a single AIS target in a boundary. I am currently thinking how to implement it so that it happens when an AIS message is received. As I intimated, this is the skeleton of the Guard Zone stuff.

Jon..Sean..
This will for sure be fine. The Watchdog changes will though need its new header
C:\Builds\OCPN\watchdog_pi\src\Alarm.cpp(40): fatal error C1083: Cannot open include file: 'AIS_Target_Info.h': No such file or directory

Håkan,
I missed out on uploading the new file. I have submitted an update for that. I have also submitted an update which I think will allow each AIS message to be checked as it is created rather than on the timer. I have also submitted another update to the mainline AIS to try and ensure that the information being supplied has been properly initialised.

You should be able to make sure everything still works at the moment, but until the change to the AIS code is implemented you will not be able to test the new functionality.

I have now managed to test the Guard Zone code with an AIS 'test' data feed and check that it works. I have submitted a new patch to Watchdog to disentangle the AIS and OD messages. I have also put up a new patch, 592, for OD to provide the name and description of the Guard Zone that has triggered the alarm.

I believe that Guard Zones now works with AIS data using Boundaries with specific GUIDs (like a reverse anchor watch). It would be interesting to here if anyone has a live AIS feed to check this out with.

You will need to compile OD and Watchdog with the my patch, not sure if it has been accepted yet, to get it working correctly. I think I also need the alarm message box to show some ship details so that you know who has encroached the guard zone. I may get to that tomorrow.

As Jon has advised earlier, there is no relationship between the Boundary and Boundary Point graphics for "inclusion, exclusion, neither" selections and the Watchdog Alarms. For example a Watchdog (WD) "Anchor" alarm can be set using a Ocpn_Draw (OD) Exclusive Boundary or Exclusive Boundary Point with Ring, (hatched interior) and the anchor alarm will still work when the Own Boat moves out of the boundary area.

In WD when setting an anchor watch alarm, it is best to have own boat located within the boundary before "Get Boundary Guid" otherwise the wrong GUID may be found.

When setting WD alarms for GPS course & time and GPS fix which are essentially WD "exclusion" alarms, the alarm sounds when the condition is reached regardless of the OD graphic appearance of the boundary (inclusive, exclusive, neither). Also these WD alarms are searching for crossing of ANY boundary, so the boundary GUID is not necessary.