OpenCPN Beta test 4.1.1108 Release

[rgleason]

Just saw your note bdbcat. If the above does not help, perhaps I can do a "bisect"

[rgleason]

Bdbcat:

If the effect you are seeing is recently introduced, you should try to do some git-bisect loops to identify the offending commit.

The idea is to go back in time to find a github commit that builds and seems to work correctly, and then let git help you find the later commit that breaks something, which it does by a binary search. Presumably, the offending commit happened after the commit proven to work, and before the most recent HEAD, which you declare broken. You just need to find it, and then inspect the code diffs for that commit.

There are plenty of git-bisect tutorials online, and it is a good tool to have in your set when this type of thing happens. It is far better than trying to run random builds you find floating on your file system, since you may have no idea really where those builds came from.

We can help you get started...

Yes, I'd like to learn this. Did it once a long time ago.

Question about:

It is far better than trying to run random builds you find floating on your file system, since you may have no idea really where those builds came from.

I do know where these compile came from (don't I?)
Opencpn_4.1.1108_GIT10- 5a7d84d- Merged Pull Request 526 -tdan
opencpn_4.1.1108_GIT9- cba9f98- Merged Pull Request 519-Ptizef
opencpn_4.1.1108_GIT8- df06bed- CorrectPersistentOptionSerialdetect
opencpn_4.1.1108_GIT7- 32ee195- AddMissingImagefiles

The funny letters and numbers are the Git Commit Numbers from here:
https://github.com/OpenCPN/OpenCPN/commits/master

and here is MPR#526 from TDan, for example:
https://github.com/OpenCPN/OpenCPN/c...a21b4fab5bca2e

I know where these compiles came from. Can't I use these compiles for a start?

Got it now. http://webchick.net/node/99

[rgleason]

First I decided to test
Opencpn_4.1.1108_GIT10- 5a7d84d- Merged Pull Request 526 -tdan

further, by running CM93 charts again, with off=Show Chart Outlines.
They worked fine. Then I turned on=Show Chart Outlines
It worked for awhile zooming and panning in Norway with Display Selection = All so there was lots of details and work. There were no black screens and not much pause at all. Then I wondered if that was the problem...cpu=0%-30% mem=356mb so after a couple more zooms and pans, I decided to click on the chart with the mouse, at that instant everything changed, black screens, difficulty panning and zooming, menu got really slow, and would not respond. I was able to open Options and tried to turn off = Show chart boxes but could not. Have been trying to shut down opencpn now 3 xs and will have to kill it.

Then opened Opencpn 4.0 and turned off= Show Chart Outlines. Closed and opened v4.1.1108 and Show Chart Outlines was off. Also CM93 charts work fine.

So we know that at least one problem is "Show Chart Outlines".

Just for yucks I turned on="Show skewed charts north up" and zoomed and panned at close scale from Hammerfest to Grytoey Island . No problem here.

Now I am going to find out where on=Show Chart Outlines was working.

[rgleason]

I installed
opencpn_4.1.1108_GIT7- 32ee195- AddMissingImagefiles
Dec 19 AddMissingImagefiles
32ee195ca3499e2994dc6402a6794b1dd760402d

and Tested with off=Show Chart Outlines ---> Works fine
then on=Show Chart Outlines ---> Terrible, eventually failed, black screens and menus were extremely reluctant. (It worked okay, but choppy for awhile, and I almost thought it would not fail, but eventually it did).

So the problem is before Dec 19 and I have no compiles from that earlier time.
I think I have to go back to before a series of chart improvements and optimizations one of which was for adjusting chart outlines to make it faster?

[P_Dub]

With the beta version 4.1.1108 in Windows, there is no problem at all.
Windows 7 Ultimate and 8 gig of ram. So be carefull before changing anything not to go back to the previous version problem.
Regards.

[bdbcat]

Ahoy Beta Builders...

Thanks to a burst effort by Pavel (nohal), we have pushed a significant update to github master.
We now support vector graphics format (SVG) for our toolbar tools and other icons. This gives us much better rendering of icons when scaled, and better images all around.

If you are build OCPN from github source, there are some new build dependencies which must be satisfied.

On all platforms, SVG support can be disabled by -DOCPN_USE_SVG=OFF cmake parameter
On Linux, we try to use GTK2 and if it is not found, look for GTK3. GTK3 dependency can be forced by -DOCPN_FORCE_GTK3=ON

Inclusion of wxSVG adds dependency on Expat and Cairo (and their dependencies like Pixman, LibPNG, Iconv, Fontconfig and LibXML2)

Prerequisities:

OS X:

brew install cairo

Linux:

apt-get install libexpat1-dev libcairo2-dev

or equivalent

Windows:
All the needed files included in the dependencies bundle (As part of the process the openssl dependency was dropped and cURL included to 9.46 + using the same ZLIB as the GTK libraries), the updated bundle is available at
Download opencpnplugins from SourceForge.net


The vector graphics bundled into the package are placed in

data/svg/<STYLESYSNAME>/

We need some feedback from builders to ensure that we have the dependencies all identified correctly. And, of course, feedback on performance and appearance.

There are some known problems with a few icons which are under review now. Let us know what you see, as well.

Thanks, and good luck building
Dave

[rgleason]

Did-g has been making some great improvements to charts which I've been watching in the github message flow. I believe I noticed one for Chart Outlines improvements and I have been searching back to Nov 21 for that commit.

Is there a good way to do searches on this commit list?
https://github.com/OpenCPN/OpenCPN/c.../master?page=9

Also including the details in the Pull Requests?

I have not found such a search yet.

I want to compile a version just before that commit.

Later- Found this search put in Filters isr is:closed author:did-g
https://github.com/OpenCPN/OpenCPN/p...uthor%3Adid-g+

Could not find anything that looked right. So did search on "outline"

https://github.com/OpenCPN/OpenCPN/s...C%93&q=outline

These are likely areas where the problem may be?
include/cm93.h
Showing the top three matches. Last indexed on Sep 27.

See // shared outline drawing buffer

[rgleason]

Does anyone else with a SurfacePro3 have trouble with the current beta when
ON = Show Chart Outlines
with Opengl=ON and Texture Cache=ON?

Doesn't anyone else (any computer) have this problem?

@P_Dub

With the beta version 4.1.1108 in Windows, there is no problem at all.
Windows 7 Ultimate and 8 gig of ram. So be carefull before changing anything not to go back to the previous version problem.

P_Dub, Please try the above settings. Thanks.

[rgleason]

Not going to compile a version back as far as Sept 23, I am going to wait to see what happens.

[Hakan]

Dave..
re:"We need some feedback from builders..............."

Build in Win10 VS2013 w/o errors for both release and package.

Runs as usual and I see no differences, but I use Journeyman
The Traditional tool icons are significant bigger than Journeyman and won't fit one row as J's does.

So far I haven't seen any other changes. Please advise what to look for.

Håkan

[Hakan]

And the VS2013 build runs fine on WinXP.
VS2010 failed to build but that's as expected I suppose.

Håkan

[nohal]

Originally Posted by Hakan

And the VS2013 build runs fine on WinXP.
VS2010 failed to build but that's as expected I suppose.

Håkan

Hakan...
Yes, for now, I need to dig out an old VM to build the required libs with VS2010. If there still is interest for them. Honestly, I would much prefer not having to

Pavel

[bcn]

Originally Posted by nohal

Hakan...
Yes, for now, I need to dig out an old VM to build the required libs with VS2010. If there still is interest for them. Honestly, I would much prefer not having to

Pavel

Scenarios you have in mind for that?
How many XPs left at all?

And Microsoft's snow plough way to force W10 will leave relatively few W7 and W8 installs left as well. But some will stay there.

[nohal]

Originally Posted by bcn

Scenarios you have in mind for that?
How many XPs left at all?

And Microsoft's snow plough way to force W10 will leave relatively few W7 and W8 installs left as well. But some will stay there.

Windows XP (Or any other version) user machines are not affected at all, OpenCPN still runs on them without any changes.
What is affected are legacy developer machines with Visual Studio 2010 (Our official toolchain is Visual Studio 2013) Building the dependencies will most likely take something like a whole day of fighting the problems, so I would prefer not to do it if nobody needs it anymore...

Pavel

[bcn]

Xcactly...

Any developer who needs VS2010 left? Shout now (with arguments), please!

Btw.: VS2015....