Bad grib display on Raspberry (Openplotter)

[verkerkbr]

Originally Posted by Andreas29

Hi,

Bram, the problem is, that I didn´t use the zygrib-plugin since yet (and have no experience with it) .
I only use the build-in grib plugin from OC. This worked fine since the raspian default pre-installed web-browser changed from epiphany to chromium.
So I just changed the web-browser and it works.
The other way is to use the zygrib-plugin like you do. So I´ll give this a try, cause you said it works fine.

@rgleason: I can do this, but give me some time (a week or so)

Regards

Andreas

There are more browsers available like Firefox and now also Vivaldi for the Raspberry Pi.

[rgleason]

Originally Posted by rgleason

Andreas, would you mind writing this up so it is very clear, what happens, with screenshots if you wish, in the Tracker?

Put it under the Task Dropdown " 11- pi-Grib"
https://opencpn.org/flyspray/index.p...index&switch=1

Identify it as a Linux bug please, This "Select" function needs some improvement and could be simplified I think, but it might be limited by wxWidgets too. Thanks.

You'll need to register, then log in.

Sorry trying to do too much at once This is the link.
https://opencpn.org/flyspray/index.p...index&switch=1

[sailorF54]

Originally Posted by nohal

FWIW, with the current code from master, you should not need to patch the code manually anymore. Just set the physical display width correctly in the Toolbox and the grib plugin should honour it and work correctly.

Pavel

Hi Pavel

I have to disagree. I compiled O two days ago from git (Raspberry 3), set the width of the screen in the toolbox, and the problem is still there...

[nohal]

Originally Posted by sailorF54

Hi Pavel

I have to disagree. I compiled O two days ago from git (Raspberry 3), set the width of the screen in the toolbox, and the problem is still there...

And the patches mentioned, which in effect do exactly the same, just manually, do help you? Sorry to ask like an idiot, but I do not have the hardware to reproduce this.

EDIT:
And can you confirm the source you built does contain the following two lines (= is up to date)?
https://github.com/OpenCPN/OpenCPN/b...oLine.cpp#L174
https://github.com/OpenCPN/OpenCPN/b...ctory.cpp#L221

[sailorF54]

Originally Posted by nohal

...
And can you confirm the source you built does contain the following two lines (= is up to date)?
https://github.com/OpenCPN/OpenCPN/b...oLine.cpp#L174
https://github.com/OpenCPN/OpenCPN/b...ctory.cpp#L221

Yes, both sources seem up to date... (see pics)
A shot in the dark: Is there a way to check that the screen size is reported accurately by the Raspberry ? I noticed that my screen is 1280 x 800, which is not standard (1280 x 720),and I have to use the default setting (= monitor preferred resolution)

EDIT
I have forced my display to 1280 x 720, and tried various values of screen size in O, but to no avail...

[nohal]

Originally Posted by sailorF54

Is there a way to check that the screen size is reported accurately by the Raspberry ? I noticed that my screen is 1280 x 800, which is not standard (1280 x 720),and I have to use the default setting (= monitor preferred resolution)

Yes, in the logfile, you should see something like

18:50:56 -03: Metrics:  m_display_size_mm: 286     wxDisplaySize:  1280:800

[sailorF54]

Originally Posted by nohal

Yes, in the logfile, you should see something like

18:50:56 -03: Metrics:  m_display_size_mm: 286     wxDisplaySize:  1280:800

The values in the log file are correct
m_display_size_mm: 220
wxDisplaySize: 1280:800


EDIT
When I change my display size to 1280 x 720 and the width screen to 200 mm, the log reports the new values correctly

[nohal]

Just two things come to mind:
- Restart of OpenCPN is required for the change in display physical size to take effect in the grib plugin. I suppose you did this
- Make sure you really run the version you built yourself, not the one provided by OpenPlotter. (You can see where your plugins are loaded from in the log)

[sailorF54]

Originally Posted by nohal

Just two things come to mind:
- Restart of OpenCPN is required for the change in display physical size to take effect in the grib plugin. I suppose you did this
- Make sure you really run the version you built yourself, not the one provided by OpenPlotter. (You can see where your plugins are loaded from in the log)

1 - Yes I did
2 - It must be the compiled version, as I have the 'All GSHHG basemap' you so kindly provided. Also the grib_pi folder is dated from 2 days ago

EDIT: SILLY of ME... I made a launcher to the old CPN version... Using the compiled one, the grib display is correct


SO SORRY to have bothered people !!!

[nohal]

Originally Posted by sailorF54

2 - It must be the compiled version, as I have the 'All GSHHG basemap' you so kindly provided. Also the grib_pi folder is dated from 2 days ago

Well, "must be" is definitely not as good as "is" for me What is a "grib_pi" folder? Did you "make install" your build products and do you really run them and only them? If you did no change anything, your installed OpenCPN should be under /usr/local) and the log should confirm that the libgrib_pi.so is loaded from there and the API version it uses is 115, is it so?

[sailorF54]

Originally Posted by nohal

Well, "must be" is definitely not as good as "is" for me What is a "grib_pi" folder? Did you "make install" your build products and do you really run them and only them? If you did no change anything, your installed OpenCPN should be under /usr/local) and the log should confirm that the libgrib_pi.so is loaded from there and the API version it uses is 115, is it so?

I repeat
SILLY of ME... I made a launcher to the old CPN version... Using the compiled one, the grib display is correct

SO SORRY to have bothered people !!!