OpenCPN for Android Beta test 4.1.818

[Hakan]

Originally Posted by HappySeagull

^ you guys.
What are you talking about? Why are you in the Android Beta thread?
Unless you are all running emulators? Or I am guessing the version numbers of BetaComputer O and Beta Android O are the same?

Happy...
We are talking about the same code and that 4.1.818 shall still be fully usable on all environment. So I'm testing backward compatibility. - Right?
Håkan

[CarCode]

Originally Posted by Hakan

Happy...
We are talking about the same code and that 4.1.818 shall still be fully usable on all environment. So I'm testing backward compatibility. - Right?
Håkan

I vote for splitting the code into a computer part and an Android part.

Gerhard

[Hakan]

Originally Posted by CarCode

I vote for splitting the code into a computer part and an Android part.
Gerhard

-- And one Google part and one Mac part and one Win part and one GTK part and one RB_pi part and..... I don't agree. Still is the main part of the code equal.
Håkan

[CarCode]

Originally Posted by Hakan

-- And one Google part and one Mac part and one Win part and one GTK part and one RB_pi part and..... I don't agree. Still is the main part of the code equal.
Håkan

Please read the code first...
Gerhard

[bdbcat]

Gerhard...

We are working, however slowly, to move platform dependencies over to the OCPNPlatform class, so that the core code can remain somewhat pure of numerous #ifdefs. The result will be imperfect, of course, but at least easier to read.

Its a work in process, lots to be done. But we think of it everytime a new feature is added, or special case for Android.

And honestly, we don't much care how ugly the git repo history looks. Its the resulting code that counts.

Of course, help in the nature of Pull Requests is gratefully accepted.

Dave

[CarCode]

It's not only the hard to read code style, it's also the fact that often commits results in new errors of functions which has been worked before, e.g. the object query window is dead since several weeks.

Gerhard

[HappySeagull]

Originally Posted by Hakan

Happy...
We are talking about the same code and that 4.1.818 shall still be fully usable on all environment. So I'm testing backward compatibility. - Right?
Håkan

Thanks,Hakan.
a.k.a. "The Unified Field Theory". I was wondering...

[tom_BigSpeedy]

Originally Posted by tom_BigSpeedy

3) I cannot switch from CM93.2 to BSB raster charts anymore. Whenever I move the mouse over the (correctly visible) chartbar it disappears. No chance to click ...

With the latest (yesterdays) commits, the behaviour changed for me.
As soon as I resize the O main window (click and drag the frame) I see the chart bar. It shows the symbols for BSB and CM93.2. As soon as I move the mouse into the O window, the chart bar disappears.
But I can click (as to say : blind) at the positions where the chart bar symbols were visible before, and wonder oh wonder, charts are changing as expected.

So it's an issue of displaying the chart bar ...
No change wether OpenGL on or off

Colour of currently running track still wrong.

VC2013, Win7, 64bit, compile release ...

Thomas

[seandepagnier]

I can reproduce this problem by cross compiling opencpn with mingw and running it in wine.

This means I can quite easily fix the problem, but the real issue for me is I have too many open pull requests already, so I am currently only developing plugins. I really need to push the mingw stuff as it's impossible for me to fix windows specific problems without it.

[bdbcat]

Thomas/Sean...

I just pushed a quick fix for the disappearing chartbar in DC mode. As written, we don't get the advantage of not having to render charts under the chartbar, and we render the bar on every frame paint. So, no real performance improvement yet in DC mode.

A better way would be to cache a bitmap of the (opaque) chartbar, update that cache on chartbar changes, and simply blit the cached bitmap to screen as required. Cleaner logic, I think, with less region calculations.

Dave

[seandepagnier]

Originally Posted by bdbcat

Thomas/Sean...

I just pushed a quick fix for the disappearing chartbar in DC mode. As written, we don't get the advantage of not having to render charts under the chartbar, and we render the bar on every frame paint. So, no real performance improvement yet in DC mode.

This is great for now, eventually we will get it right.

A better way would be to cache a bitmap of the (opaque) chartbar, update that cache on chartbar changes, and simply blit the cached bitmap to screen as required. Cleaner logic, I think, with less region calculations.

Dave

I tried already both ways, it's really not a problem to render the rectangles, and in most cases it's faster, and either way it makes no difference for performance (I profiled it) and it's simpler to not have an extra cache bitmap.

[tom_BigSpeedy]

Originally Posted by bdbcat

Thomas/Sean...

I just pushed a quick fix for the disappearing chartbar in DC mode.
Dave

Dave,
I just compiled latest commits under VC2013, Win7 and gave it a try.

Chart switching and chartbar behaviour works fine for me now.

Thomas

[Cat-Man-Do]

Hi all, GREAT WORK :-) ... I have successfully installed this application on a Samsung Tab 7 Note 10.1 and Tab 8.4 all running KitKat and all seems well with CM93 charts, I have also installed it on a Samsung Note 3 and S5 both running Lollipop after initial GPS location the programme seems to lock up and won't update from the GPS:-( I thought I saw somewhere an updated APK version 4.1.9??? is this still about?
Regards
Niel

[bcn]

There is a production version out as an official Android App:

https://play.google.com/store/apps/d...pencpn.opencpn

[OceanSeaSpray]

Originally Posted by Cat-Man-Do

...
I have also installed it on a Samsung Note 3 and S5 both running Lollipop after initial GPS location the programme seems to lock up and won't update from the GPS
...
Regards
Niel

This is interesting as it has also been the behaviour on the Galaxy S4. However it only locks up if speed is involved and the vessel's position is within the plotting area. Acquiring a static fix is ok on the S4.

Eric