GPS based Odometer

[sv_pelagia]

Have changes/fixes also been apied to the Android version?

[LennartG]

sv_pelagia,
sorry but I am still trying to figure out what is going on there, it appears to be a compiler problem triggered by the program.
Are not sure where to look as Windows, Linux and MacOS does not have this problem.
/LennartG

[rgleason]

The android version does not work and will freeze your OpenCPN and you will have to edit the config file to start Opencpn again.


There is a error message posted below, then you are able to get into Preferences but none of the preferences work. Hit continue and Opencpn will freeze and you will not be able to open it again until you edit the config file. Using an android text editor found the opencpn.config file and searched for gps-odometer. Set benable=0. No dice. Then realized that I had saved space by putting it on my extSD card, so found that opencpn.config file and tried changing that. Only found "persistance" under gps-odometer and set that to 0. Now it seems to open....


Lennart, Android requires to have certain if android then statements put in it to work properly. I have the same problem with Celestial_Navigation. Bdbcat has given us some good direction by fixing Climatology, use my git repository rgleason/climatology I believe it is in the master branch. I think if you look at climatologydialog.cpp and climatology_pi.cpp you will see some of these statements. I have not figured them out.

[sv_pelagia]

Fortunately, turning on GPS Odometer on my Android tablet (Android 10) has not resulted in a non-working OpenCPN.

(But I never tried using it with GPS on or a VDR sequence - - didn't like the error message shown above -- so perhaps this is why my Android OPCPN did not freeze?)

Have disabled this plugin on android version.

[LennartG]

sv_pelagia and rgleason,
odd thing is that 'm_orient' is not even used in the GPS Odometer, it is imported from somewhere else, trying to find from where. 'orient' is used but that is a different matter.
I will look closer into the suggestions from rgleason, that could be useful.
/LennartG

[CarCode]

There are some rules using sizer flags which have been always omitted by the programmers. The correct use of sizer flags has been always explained in the wxWidgets docs but nobody cared about it. Some compilers produce crashing code but others not. So in later wxWidgets versions an assert function was introduced to force programmers using correct code.


Thumb rules for sizer flags are:
- don't use horizontal alignment flags together with wxWXPAND
- don't use vertical alignment flags together with wxWXPAND
- don't use horizontal alignment flags for horizontal sizers
- don't use vertical alignment flags for vertical sizers


I know a programmer who never understand this...

[Gilletarom]

Originally Posted by LennartG

Gilleratom,
....
Note about the buttons: These are of fixed size so please be careful with the text string length.
....
/Lennart

The translation of the language file on the crowdin is done.

Having said that, you will have to take into account that the French language uses a lot more characters than the English language to say the same thing.

So if you impose too little space, the items may not display correctly. For example, "Reset" should translate to "Remise à zéro". The French language is certainly not the only one which has this drawback.

Gilletarom.

[rgleason]

Thanks very much Carcode, this is very helpful.
"Thumb rules for sizer flags are:"

[LennartG]

Release 0.3.2 of GPS Odometer is now available for download through the OpenCPN package manager.

This release fixes the instrument order problem in Windows and adds a number of new languages (more are to come) plus a number of minor fixes.
The problems on android are not yet solved, sorry for that, and the community is invited to assist.
Note that NMEA signals RMC and GGA are required for the GPS Odometer, it will not display anything unless both of these signals are present.

The internal plugin name has been changed so it is recommended, but probably not required, to clean out the configuration file from previous GPS Odometer information following this procedure (Please click the 'Question Mark Icon' for information where to find the file):

Take note of the current 'Sum Log Distance' or the value will be lost.
NOTE: Stop OpenCPN before doing any of these changes!

There may exist alternative names for the plugin, containing 'odometer':
1. Remove everything from and including '[PlugIns/gps-odometer_pi.so]' (anything containing 'odometer') down to the next opening square bracket for the following config item ('[')
2. Remove everything from and including '[PlugIns/libgps-odometer...]' (or anything containing 'odometer') down to the next opening square bracket for the following config item ('['). This section only have two lines.
Please note: Do not remove the opening square bracket for the next configuration item.

Start OpenCPN again, you need now reactivate GPS Odometer again in the plugins menu.

If you have a recorded 'Sum Log Distannce', please do:
- Stop OpenCPN again
- Update the value 'TotalDistance' as noted
- Restart OpenCPN

Last but not least: A great thank you to all the people (no one mentioned, no one forgotten) who have assisted in getting language translations added, could not do it without you.

/Lennart