SaltyPaws Plug-in SAR

[SaltyPaws]

I am dusting of the plugins, and now is the turn for SAR_pi. I have now embedded the image files, into the code, so it is easier to see what the parameters in the SAR window stand for. The attached image gives an idea of how it looks.

Executables can be found here: libcalculator_amd64_pi18_v13_pi

Gilletarom: Could you send me a pull request for the french language file. I will have a look at your suggestions.

[rgleason]

This thread looks like the right one. Salty Paws here is the output to recent compile.
Also sent private message, but they do not support attachments.

These changes with icons look pretty good.

[SaltyPaws]

The build issue should be fixed. I had to swith to bin2c to embed the images, source grew with 700kb..... Windoze is just a little less flexible than linux I suppose. Could you try again?

[rgleason]

Okay, it compiled
SaltyPaws, I will test it later. Thank you.

Attached as doc. Take doc off and put in your plugins dir to test.

[Gilletarom]

Hello Salty Paws,

I have a little time today to look at your plugins. I worked on the language file CALCULATOR.

The pot file was online here: https://github.com/SaltyPaws/calcula...tree/master/po

But it is 5 months old..

It is not up to date. Missing two item: "History" and "Max results".

Can you update?

In the meantime, here is a slightly improved french file language.

Best regards

Gilletarom

[Gilletarom]

Hello SaltyPaws,

I see that you have updated the french file language for CAlculator. This is well.

But you have not updated the pot file. There is two new items :"History" and "Max results". These two items are not in pot file.

Please, update the pot file. And then I will work for an other french version of po file.

B.R. Gilletarom

[rgleason]

Tracker VOTING for Plugins has been enabled by Serge. Please VOTE in Tracker for all Plugin projects (upper right dropdown) for the Feature requests you'd like. Also please do make comments and add Feature Requests and Bug Reports. You'll need to register or log in to Vote, add items and make comments.

Tracker VOTING.
SAR

[rgleason]

Tracker has a report that there is a bad bug in the SAR_pi which results in waypoint errors of 1.8 nm and more.
https://opencpn.org/flyspray/index.p...s&task_id=2110

If someone can fix this problem it would be great.

SAR_pi is a safety plugin so this problem is not good.

[rgleason]

This is a request to any willing programmer to fix SAR_pi, which is a search and rescue plugin.

Gilletarom has identified a "bug" with an 1.8 nm error and as a result we have removed the plugin.

The Git Source: https://github.com/SaltyPaws/SAR_pi

Tracker bug report: SAR_pi which results in waypoint errors of 1.8 nm and more. https://opencpn.org/flyspray/index.p...s&task_id=2110


Enhancements needed:
1. Create a SAR route in OpenCPN on command.
2. Allow entry of Set & Drift estimates which will show a boxed offset.

Gilletarom and I are available to help in any way and test. We would like to get this working for v4.8.2

[rgleason]

Gilletarom please see https://opencpn.org/flyspray/index.p...s&task_id=2110

I believe you have used degrees & decimal minutes for this plugin and it does not accept that format. Use decimal degrees and I believe it works properly.

[rgleason]

New Tracker Feature Request
FS#2342 - API 1.15 Lat/Long Format for waypoint copy/paste Interoperability

[Gilletarom]

Hello,

Originally Posted by rgleason

New Tracker Feature Request
FS#2342 - API 1.15 Lat/Long Format for waypoint copy/paste Interoperability

Page not found.

Seach here :
https://opencpn.org/flyspray/index.p...r=id&sort=desc

[Gilletarom]

Hello RGleason, Hello Walter Shulpen,

I confirm the error noticed by Pfalexis in the task FS#2110 - Conversion error. dangerous result !

See what I write in this page : https://opencpn.org/flyspray/index.p...s&task_id=2110
Gilletarom.

[rgleason]

Gille, In my opinion, it is a dangerous user error that should be remedied. If the correct format is entered it works. However if the wrong format is used there is an incorrect result. This should not happen.

[rgleason]

With so much progress getting the Opencpn v4.8.2 plugins language files updated, bug fixes and improvements, I thought I'd make a plea to get SAR_pi working acceptably.

Unfortunately there is a problem when the user enters Lat/Long in the wrong format and gets back a result that is unintended and completely different than it should be.

The immediate fix is to have a prompt, Is this Lat Long in the correct format? ( whatever format is required )? whenever there is a question about what has been entered.

The long term fix is to use the exact same Lat/long format everywhere (opencpn and plugins) whenever there is copy and paste operation. Thus everything is speaking the same format! Then Opencpn or the plugins can display the result in whatever format has been selected by the user.

I'd like to propose that we try to move towards the "Copy Lat/Long" being only in Decimal Degrees (DD) because it is easiest and simple. It can be converted to Degrees + Decimal Minutes (DDM) or Degrees, Minutes, Seconds (DMS) for display.

With that in mind can we possibly get SAR_pi out of the hospital (she was placed there sometime ago because this problem involves safety) and back on the downloads page?

Are there any program volunteers willing to take a look?

Thanks.

FS#2178 - Speed entered into search pattern is not being imported into route and mark manager

FS#2110 - Conversion error. Dangerous result!


I think insofar as windows is concerned many of the plugins have been updated with language files, fixes and improvements such that the should be ready for their final resting spot with Opencpn v4.8.2 before moving onto the next version. I'll try to make a plugin list to see where we are. If you have time and inclination, it would be a good idea to do some testing of your favorite and most used plugins if they have been updated on the downloads page.