Logbook Konni for OpenCPN

[Tenedos]

Originally Posted by Rasbats

I suggest using delatbabel as the main code source:

https://github.com/delatbabel/LogbookKonni-1.2

My fork is in synch with delatbabel. I am doing Windows releases from my fork. Suggest we use delatbabel as the ultimate source, to avoid confusion. Ptulp is doing a great job implementing pull requests for delatbabel from other forks.

Mike

Thank you Mike. Is anyone currently building macOS releases? I see there is a Logbookkonni-Plugin_1.3006.pkg but it is not clear if it is compatible with OpenCPN 5.0. According to this page, there is no release for 5.0, I am not sure if this is up-to-date though.

[Rasbats]

Tenedos ...

Ptulp compiles for the Mac but he is pretty busy at the moment. It would help if you worked on this.

Mike

[Tenedos]

Originally Posted by Rasbats

Tenedos ...

Ptulp compiles for the Mac but he is pretty busy at the moment. It would help if you worked on this.

Mike

Ok, never compiled an OpenCPN plugin before but I will give it a go later today or tomorrow.

[rgleason]

We really need someone familiar and using MacOS and programming to work on plugin compilation!


I believe it is also possible once the plugin is programmed properly for Windows (appveyor) and for MacOS and Linux, to use .travis to compile the plugins for osx almost automatically.


This might be a very worthwhile endeavor for MacOS users.


You would need a .travis account to do this, but that is free for opensource and if you have a free opensource github account I believe.

[Tenedos]

Originally Posted by Tenedos

Ok, never compiled an OpenCPN plugin before but I will give it a go later today or tomorrow.

Ok, I have compiled it but I couldn't get it to work, seems to be some issue with wxWidgets. I compiled 3.0.4 from source, tried the one that comes with homebrew (README mentions not to use it but tried just in case), and finally compiled 3.1.2 from source, all to no avail. This is the error in OpenCPN logs when I try 3.0.4:

08:21:23 PDT: Error: dlopen(/Applications/OpenCPN.app/Contents/PlugIns/logbookkonni_pi/liblogbookkonni_pi.dylib, 2): Symbol not found: __ZN12wxWindowBase19SetVirtualSizeHintsEiiii
  Referenced from: /Applications/OpenCPN.app/Contents/PlugIns/logbookkonni_pi/liblogbookkonni_pi.dylib

When I use wxWidgets 3.1.2, compilation fails with some incompatibility errors, 3.1.X is backwards incompatible with 3.0.X and clearly the plugin does not support 3.1.2 yet (I do see a pull request though, anyone knows the state of it?).

Also reading the OpenCPN docs, my understanding is 5.0 is using wxWidgets 3.1.2. Is that correct? If so, how is it possible the plugin was compiled for Windows with 3.1.2 support? (According to the plugin page, Windows plugin is available for 5.0).

Any pointers from anyone?

[Tenedos]

Originally Posted by Tenedos

Ok, I have compiled it but I couldn't get it to work, seems to be some issue with wxWidgets.

Ok, I solved it. I have a working macOS binary for OpenCPN 5.0.

For those interested, here is the reason: wxWidgets 3.1.2 support was already introduced and it is required for OpenCPN 5.0. However, some macOS specific code snippets were not updated, that was the culprit. That must be the reason why it could be compiled for Windows but not for macOS.

I also sent a pull request to push the changes into the repo.

I can send the binary if someone is willing it to put it to the github release page and update the plugin page.

[rgleason]

Quick learner here. Sorry I was not online. Thank you Tenedos!

[Dockhead]

Hi: I like your logbook so much, that I use it exclusively! No more paper logbook for the last few years.


However, my ship's computer has a problem with its internal clock, and I've discovered something which may be a bug, or may be just a user error . The log insists on using system time for all purposes, no matter how I set the options "UTC", "Local = UTC + ___", or "GPS Auto".


I would like to be able to make the logbook ignore system time and exclusively use GPS time. Is there some way to do this?


Thanks for all your good work!

[ptulp]

Dockhead,

Could you do the following test:
Using the VDR plugin, could you run the attached file and while the file is playing Add a line in logbook and see what the date and time are showing.
It should be a date of 20-10-2012 and a time around 11:16 if the GPS Auto is set in the preferences.

Remove .pdf form the file.

[Dockhead]

Originally Posted by ptulp

Dockhead,

Could you do the following test:
Using the VDR plugin, could you run the attached file and while the file is playing Add a line in logbook and see what the date and time are showing.
It should be a date of 20-10-2012 and a time around 11:16 if the GPS Auto is set in the preferences.

Remove .pdf form the file.

OK, I'll do it now. Thanks.

[Dockhead]

OK, so I get date 31.12.-014 at 14:00, and an "information" popup -- "Please enter the Date in the format: 01.05.2019"

[Dockhead]

Sorry, with "GPS Auto" set, I get date "01.01.-013" and time "00:00:00"

[conachair]

For reference with time set to loca, UTC + 1 I.m getting the right time by the looks of it =>

[ptulp]

Originally Posted by Dockhead

OK, so I get date 31.12.-014 at 14:00, and an "information" popup -- "Please enter the Date in the format: 01.05.2019"

Strange, looks like the date/time from the NMEA message is not parsed correctly.
Very strange.

[Dockhead]

Originally Posted by ptulp

Strange, looks like the date/time from the NMEA message is not parsed correctly.
Very strange.

Looks like that. And that would explain everything, wouldn't it? So what to do about it?