Visit our Popular Forums

rgleason · 08-03-2018, 05:50

Mike, I think your cross compiling PR is fine. The bug found applies to both linux and windows I believe, and is a separate issue that may have existed before!

Looked at this, you made a PR in Jan 2017 that deals with formatting. I think you were correcting the problem?
https://github.com/SaltyPaws/calcula...c770f79ae798c7

rgleason · 08-03-2018, 06:44

Under Preferences
Precise - default
Precise (Thousands separator) - Opencpn Fails
Succinct
Succinct (Thousands separator) - Openpn Fails
Scientific
Humanized
The two that fail could be disabled or they could be fixed.
Probably has something to do with line 710

Also the function Humidex gets an error
Error: Unexpected parenthesis "(" at position 39
Which is probably unrelated.

https://github.com/SaltyPaws/calculator_pi/issues/21

I believe this is a separate problem from Cross Compiling.

rgleason · 08-03-2018, 09:34

Mike, I tried your version calculator_pi-1.7 (which shows as 1.6 in preferences) and that version does not have the precise thousands or succinct thousands error.

Perhaps line 710 as you had it is better, rather than SaltyPaws version.

Rasbats · 14-03-2019, 10:55

My fork of Salty_Paws Calculator_pi has been updated for OpenCPN 5 beta.

https://github.com/Rasbats/calculato...eases/tag/v2.0

Compiles on both Windows and Linux. Many warnings on Linux but both versions seem to work correctly. Please test.

For ease of maintenance I have removed the Fx button from the toolbar. Fx is accessed via the Calculator dialog.

Mike

rgleason · 14-03-2019, 13:29

Mike I think that is a good idea>

Rasbats · 03-04-2019, 04:06

Translators ...

A new POT file for Calculator_pi is now in Crowdin. Would appreciate help with translations where possible. There are a lot of strings in the file that will not need translation. Please ignore these. (I wanted to avoid making too many replacements!)

Mike

Gilletarom · 03-04-2019, 11:31

Mike,

It seems to me that it would be convenient to put a comment, in the comment section of the page of the crowdin, allowing the translators to recognize the items that should not be modified.

Gilletarom.

Rasbats · 03-04-2019, 14:05

G ...

Noted, but your translations are fine. You have not changed any strings that are likely to cause a problem.

Mike

Rasbats · 04-04-2019, 08:59

Just tested with some translations and the functions are not working correctly.

Suggest translators wait for an updated POT file where only "safe" strings are available for translation.

Mike

Rasbats · 03-05-2019, 13:59

With massive help from Gilletarom a number of corrections have been made to calculator_pi and it should be easier to use.

The POT file has been updated on Crowdin. Translations are complete for French but would be welcomed for other languages.

The updated Windows and DEB installers for v2.2 are here:

https://github.com/Rasbats/calculato...ov50-win32.exe

https://github.com/Rasbats/calculato....2-1_amd64.deb

Thanks,
Mike

rgleason · 04-05-2019, 06:29

Many Thanks. G and Rasbats.
I was going through the functions and found this problem

Fetch Modified Wilson

Using Knots and Nautical Miles

Error: Unexpected parenthesis "(" at position 16

Also it would be very nice if we did not have to resize the Extra Function Window every time we calculated!

Rasbats · 04-05-2019, 06:56

Rick ...

Only an error when result for waveheight is in feet. What units are you using for fetch and the result? U10 must be in m/s.

Mike

Gilletarom · 04-05-2019, 07:23

hello Rasbats,

I was right to fear that there will still be one or more bugs. And that it may remain one or more bugs despite the efforts. I counted that you had released more than 18 beta versions in a few weeks.

Bah ... It is not serious; ... A hundred times on the job we will hand over the work!

That said, for those who speak French, I created a page for "Calculator" in the website opencpn.fr:
La calculette

rgleason · 04-05-2019, 11:36

Quote:

Originally Posted by Rasbats

Rick ...

Only an error when result for waveheight is in feet. What units are you using for fetch and the result? U10 must be in m/s.

Mike

Yes now I see that there is a note that U10 windspeed must be in m/s
Also I think the formula area is not working correctly.

Fetch Modified Wilson
U10 Wind speed must be m/s
Fetch can be anything in the dropdown.
Waveheight must be "Meter"
or there is an Error
Error: Function arguments used without a function position:295)
OR
Error: Unexpected parenthesis "(" at position 16

I believe this used to complete, but somehow the values seemed to be off, but perhaps that was just me.
Mike, Did you try to get this working? IE: would it be worthwhile for me to look at it?

Yes, this is a minor bug that has been called out.