Visit our Popular Forums

Hakan · 13-06-2019, 02:30

I friend of mine got a system update on his MacOS Mojave two weeks ago to 10.14.5
After that O v 5.0 is disturbed. See shots.
I'm not at all a Mac user but the messenger. Are there any advices or actions I can pass to solve this?
Has anyone else seen the same?

Thanks
Håkan

El Pinguino · 13-06-2019, 02:38

I'm not sure if the chicken came before the egg or the egg before the chicken...ie did I download OCPN 5.0 before or after upgrading to Mojave... however..

I have a Macbook Pro Retina 13" early 2015 running Mojave 10.14.5 with no problems....

Maybe he should uninstall and then download 5 again?

Just a thought

Hakan · 13-06-2019, 02:41

El Pinguino..
Thanks. Sorry, forgot to mentioned that's one of the actions he have tried without any changes.

Hakan · 13-06-2019, 02:51

Apparently I'm not reading Mac related threads frequently. The same topic seams to been mentioned here: http://www.cruisersforum.com/forums/...ml#post2905140
Hubert has experienced the same and Pavel refers to a bug.
Are there any patches on Github master trying to solve it we can test?

CarCode · 13-06-2019, 03:25

Quote:

Originally Posted by Hakan

Are there any patches on Github master trying to solve it we can test?

He can go back to the stable OpenCPN version 4.8.8.This version works.

But if he wants to use OpenCPN version 5.0 he has to disable OpenGL.

nohal · 13-06-2019, 04:46

Quote:

Originally Posted by Hakan

Are there any patches on Github master trying to solve it we can test?

Yes, https://github.com/wxWidgets/wxWidgets/pull/1354

Hakan · 13-06-2019, 05:18

Nohal..
So if I understand it correct we've to wait for a wxWidgets update to have it incorporated in OCPN?

Meanwhile is the only solution to not use OpenGl, as of CarCode's advice, for those running MacOS Mojave 10.14.5. Correct?

Thanks.
Håkan

nohal · 13-06-2019, 06:18

Meanwhile the solution is not to resize the window as far as I can tell.

Hakan · 13-06-2019, 06:29

Many thanks, I'll ask him to try that.
Håkan

CarCode · 13-06-2019, 06:45

The patch for wxWidgets v3.1.3 works however the developer of wxWidgets doesn't know why. So the patch is actually not included in wxWidgets.

To use it for OpenCPN v5.0 the sources of OpenCPN v5.0 have to compiled with the patched wxWidgets v3.1.3 for macOS.
Maybe one of the OpenCPN developers knows why this bug is not seen with OpenCPN v4.8.8 and only shows up after OpenCPN v5.0.

nohal · 13-06-2019, 06:49

Quote:

Originally Posted by CarCode

Maybe one of the OpenCPN developers knows why this bug is not seen with OpenCPN v4.8.8 and only shows up after OpenCPN v5.0.

Because it is built by a completely different version of Xcode against a completely different version of macOS SDK. All that is completely irrelevant to solving this issue of course.

CarCode · 13-06-2019, 07:14

Quote:

Originally Posted by nohal

Because it is built by a completely different version of Xcode against a completely different version of macOS SDK. All that is completely irrelevant to solving this issue of course.

So you have to decide wether to use the old stuff and SDKs as done all the years ago or to switch finally for macOS even to beta versions of wxWidgets.
Happy coding...

nohal · 13-06-2019, 07:18

Quote:

Originally Posted by CarCode

So you have to decide wether to use the old stuff and SDKs as done all the years ago or to switch finally for macOS even to beta versions of wxWidgets.
Happy coding...

I believe you somehow missed this is what has been done for OpenCPN 5.0 since the very beginning.

CarCode · 13-06-2019, 08:28

When I have a look at the Contents folder of your OpenCPN v5.0 I see some strange things. Why you work with Aliases? And why everything is kept in the folder MacOS? Normally frameworks and dylibs are in a folder called Frameworks.