search

Rasbats / frcurrents_pi

GNU General Public License v3.0
2 stars 2 forks source link

DrawText() with OpenGL enabled on Raspberry PI causes crash #10

Open stelian42 opened 4 months ago

stelian42 commented 4 months ago

If labels for rate and direction are enabled, the frcurrents plugin will crash (somewhere deep inside OpenGL) when drawing texts.

If OpenGL is disabled, or if rate and direction labels are disabled in the plugin configuration, everything works fine.

This is not related to the number of arrows and text to be displayed, even a single DrawText() will cause the crash.

Tried on a Raspberry PI4, running OpenCPN 5.8.4 and the latest frcurrents_pi (either from plugin databased or compiled from source).

Same configuration (although OpenCPN migh be built differently) on my desktop PC running Ubuntu on x86_64 does not show the issue.

Rasbats commented 4 months ago

Thanks for the report. Now back from my sailing cruise. Should be able to look at this issue next week.

stelian42 commented 4 months ago

Thanks for your reply. There is no urgency here. And I fergot to mention, in case it matters, I am using the BBN marine OS on the PI.Le 28 juin 2024 23:03, Rasbats @.***> a écrit : Thanks for the report. Now back from my sailing cruise. Should be able to look at this issue next week.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Rasbats commented 4 months ago

New packages built here: https://cloudsmith.io/~mike-rossiter/repos/frcurrents-alpha/packages/ Not sure if the BBN OS will read this version. The version of wxWidgets used for the complilations may not match. Works for my Windows OpenCPN 5.9.2-beta.

stelian42 commented 4 months ago

Thanks, I will try the binaries and also update the repo and rebuild from source.

stelian42 commented 3 months ago

Hi, I tried with both frcurrents-1.4.1+911.22d778a_debian-arm64-12-arm64.tar.gz downloaded from Cloudsmith and with my own built from updated git, and reproduced the exact same problem.

Ptizef commented 1 month ago

Hi

Very good job But I found a problem with the Previous/next buttons around the LW. First example AREA 558/PORT NAVALO On the 15 th September 2024 there are two HW 3:47 and 16:03 (Z+2)

JP

Rasbats commented 3 weeks ago

Basic code done a long time ago. Need to study this one.

Rasbats commented 1 week ago

@Ptizef Changing direction from Previous to Next needs to capture the current state of the high water drop-downs and the time from high water before continuing. Could only fix this by requiring a second button press. The first repeats the existing state while the next continues th@Ptizef Changing direction from Previous to Next needs to capture the current state of the high water drop-downs and the time from high water before continuing. Could only fix this by requiring a second button press. The first repeats the existing state while the next continues the progression. Without a message the user may think that nothing has happened. So a message has been added.

Do you think a message is required or can we just leave the user to press twice after changing direction?

Rasbats commented 1 week ago

Had a crash which could not be repeated so the tarballs are here: https://cloudsmith.io/~opencpn/repos/frcurrents-alpha/packages/ @Ptizef ... Could you give this version a test?