I have looked at the two ini files and compared them. The only thing relevant to this is the position of the dialog which you identified earlier. I tried under windows 10 with the settings in the old ini file and see the flash as the watchdog dialog is displayed and then dissapears. I then set the dialog position to 20, 20 in the ini file after stopping OCPN, then restarted and clicked on the watchdog icon and the dialog appeared in the top left corner of the screen. I do not know how the x position got set to -5320 in the old ini, but that is definitely the issue.
A useful test would be to put back the old ini file, change the Watchdog settings to:
in the ini file when OCPN is not running then start it up again and click on the watchdog icon and see if the dialog box appears. Under Ubuntu the dialog always displays even if you have a position off of the screen.
I do not deliver beta versions to the public, they are made available by myself and others for beta testing and available either from github or Ricks test pages. The versions available from the download pages are not beta versions, they are release versions.
I have not built hard dependencies. However, if you wish to use boundaries with alarms you will need to use both Watchdog and Draw and they work
together. If you have Watchdog but not Draw then any boundary alarm
set will never fire as there will be no information provided back, this is handled. Draw does not know about Watchdog, so there is no dependency there. Watchdog does get AIS
information and this is needed for the AIS
alarms, but this is pushed to all plugins and the AIS mainline code knows nothing about Watchdog. It is possible to use a less loosely coupled communication using the ODAPI, requested by Sean, to make processing faster. But loose coupling is used to activate the API, so if Draw is not new enough the API will not be called.