OpenCPN RC 4.1.1301 Release

[NahanniV]

Latest from GIT (255a4b4981dc82051731f0c1ce36902218436c30)
will not build on ARM with wx2.8.12.
At least on my platform.

[  8%] Building CXX object CMakeFiles/S57ENC.dir/src/s52plib.cpp.o
/usr/bin/c++   -DARMHF -DLINUX_CRASHRPT -DOCPN_HAVE_X11 -DOCPN_USE_PORTAUDIO -DTIXML_USE_STL -DUSE_GARMINHOST -DUSE_GLU_TESS -DUSE_S57 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -DocpnUSE_GL -DocpnUSE_GLES -pthread -O3 -DNDEBUG -isystem /usr/local/lib/wx/include/gtk2-ansi-release-2.8 -isystem /usr/local/include/wx-2.8 -I/home/aruntu/OpenCPN/include -I/home/aruntu/OpenCPN/src -I/home/aruntu/OpenCPN/src/wxcurl -I/home/aruntu/OpenCPN/src/nmea0183 -I/home/aruntu/OpenCPN/src/mygdal -I/home/aruntu/OpenCPN/src/garmin/jeeps -I/home/aruntu/OpenCPN/src/texcmp/lz4 -I/home/aruntu/OpenCPN/src/texcmp/squish -I/home/aruntu/OpenCPN/build/CMakeFiles/include    -Wall -Wno-unused -fexceptions -rdynamic  -g -fno-strict-aliasing  -DPREFIX=\"/usr/local\" -o CMakeFiles/S57ENC.dir/src/s52plib.cpp.o -c /home/aruntu/OpenCPN/src/s52plib.cpp
In file included from /home/aruntu/OpenCPN/src/s52plib.cpp:58:0:
/home/aruntu/OpenCPN/include/glChartCanvas.h:66:30: error: invalid use of incomplete type ‘class wxGLCanvas’
 class glChartCanvas : public wxGLCanvas
                              ^
In file included from /home/aruntu/OpenCPN/include/s57chart.h:49:0,
                 from /home/aruntu/OpenCPN/src/s52plib.cpp:41:
/home/aruntu/OpenCPN/include/ocpndc.h:54:7: error: forward declaration of ‘class wxGLCanvas’
 class wxGLCanvas;
       ^
/home/aruntu/OpenCPN/src/s52plib.cpp: In member function ‘int s52plib::S52_load_Plib(const wxString&, bool)’:
/home/aruntu/OpenCPN/src/s52plib.cpp:918:31: warning: format not a string literal and no format arguments [-Wformat-security]
             wxLogMessage( msg );
                               ^
/home/aruntu/OpenCPN/src/s52plib.cpp:930:35: warning: format not a string literal and no format arguments [-Wformat-security]
                 wxLogMessage( msg );
                                   ^
/home/aruntu/OpenCPN/src/s52plib.cpp: In member function ‘bool s52plib::RenderHPGL(ObjRazRules*, Rule*, wxPoint&, ViewPort*, float)’:
/home/aruntu/OpenCPN/src/s52plib.cpp:2237:29: warning: format not a string literal and no format arguments [-Wformat-security]
             wxLogMessage(msg);
                             ^
/home/aruntu/OpenCPN/src/s52plib.cpp: In member function ‘bool RenderFromHPGL::Render(char*, char*, wxPoint&, wxPoint&, double)’:
/home/aruntu/OpenCPN/src/s52plib.cpp:8080:27: warning: format not a string literal and no format arguments [-Wformat-security]
         wxLogWarning( msg );
                           ^
make[2]: *** [CMakeFiles/S57ENC.dir/src/s52plib.cpp.o] Error 1
make[2]: Leaving directory `/home/aruntu/OpenCPN/build'
make[1]: *** [CMakeFiles/S57ENC.dir/all] Error 2
make[1]: Leaving directory `/home/aruntu/OpenCPN/build'
make: *** [all] Error 2
aruntu@aruntu:~/OpenCPN/build$

[seandepagnier]

You must compile wx 2.8 with opengl support, or install the opengl libraries of wx

[jongough]

Hi,
I have just compiled OCPN on a PI2 at the latest patch level and it works. Looking at your output the only thing that appears different is the first include where you have gtk2-ansi-release-2.8 and I have gtk2-unicode-release-2.8. My file came from installing libwxgtk2.8-dev. I also have installed:
wx2.8-headers
wx2.8-i18n

Check to make sure these are all installed.

Jon

[rgleason]

Wdkester, Sean programmed chart slider. Look in file thingie. 4.1.1108

[cagney]

Using a few days old git.

Menu Problem

Options-Ship-AIS Targets - Allow attenuation was off.
Still, some targets were smaller.
Menubar-AIS-Attenuate... was ticked, but greyed out.
I then activated the Options-Ship-AIS Targets - Allow attenuation.
Targets as expected, were off, and showed various sizes.
Next, I unticked the menubar option, and all targets were large again.
Going back to Options-Ship-AIS Targets - Allow attenuation... this option was still ticked ???

----------
Enc chart problem.

Puerto Rico Charts
a:25663_1.kap
b:US5PR55M.00
c:US4PR30M.000

Position
18 18.200 N
65 35.270 W

We should see a red and green buoy, both north and south of this position.
Vector charts in quilting mode, scale 1:33800, only one buoy is visible, the norther green buoy.
Zoom in/out makes no different.
In single mode chart b/ shows no buoys, while c/ shows all.

Buoy problem, quilting problem or chart problem?

/Thomas

[rgleason]

Ah Thomas, you are here!
I need some help understanding how things work with the documentation..
I was going to ask Bdbcat about this outline and ask some other questions...

How does this look for the Main Outline?
Opencpn 4.1.1108 Documentation - Page 4 - Cruisers & Sailing Forums

If you and wdkester can review and make suggestions for changes, I can then go through all the docs and make sure the links are working properly. Is there a way I can do search and replace on the documents?, or at least I can use Find...?

Also I need to understand this which I found somewhere...
Opencpn 4.1.1108 Documentation - Page 4 - Cruisers & Sailing Forums

Can someone help regarding

"Links must match Heading for export"

What does this mean specifically?
When is "export" done?
Specifically which links and which headings?

I hope I am not making a problem.

Also how is export done and can I try that to see how it works and if everything is working?

Thanks

[bdbcat]

@cagney...

AIS Attenuation menu issues.

The way it should work is this:
1. The "Options->Ships->AIS->Allow attenuation...." is a global enabler switch. It does not actually activate the attenuation, just enables it with the specified target count. The state of this item does not affect the current activation state of attenuation.

2. The attenuation may be activated/deactivated by either of two methods:

a) Menubar AIS->Attenuate...
.or.
b) cycle of the AIS toolbar icon.

This is the designed operation.


In your report, there does seem to be a problem, however:

"Options-Ship-AIS Targets - Allow attenuation was off.
Still, some targets were smaller."

This seems like a bug, and I will check it.

Thanks
Dave

[rgleason]

Thomas, you are here! I need some help understanding how things work with the documentation.. I was going to ask Bdbcat about this outline and ask some other questions...
How does this look for the Main Outline? Opencpn 4.1.1108 Documentation

If you and wdkester can review and make suggestions for changes, I can then go through all the docs and make sure the links are working properly. Is there a way I can do search and replace on the documents?, or at least I can use Find...?

Also I need to understand this which I found somewhere...
Opencpn 4.1.1108 Documentation - Page 4 - Cruisers & Sailing Forums
"Links must match Heading for export"
What does this mean specifically?
When is "export" done?
Specifically which links and which headings?

Also how is export done and can I try that to see how it works and if everything is working?

I've fixed the bad links from the beginning of OpenCPN User Manual all the way through to the end of Advanced Features.

What remains left to do is FAQ and Links (with the exception of those that I may have missed.) One more pass should do it.

[bcn]

Chart objects scale factor moves object instead of scaling in case of negative factors. Windows OpenGL On/Off (from Dave's last night build)

[Gilletarom]

Hello Dave,

I am currently testing the OD plugin.
I notice that on my tablet (touchscreen, 2560 x 1600), it is completely impossible to change an area because the icons are too small and impossible to select with my thinger.
But this is a general problem with all plugins. I understood that you had considered this problem and you will solve it with the collaboration of developers plugins. Congratulations in advance.

There is another subject that seems important to me It is the absence of harmonization of how to create and/or edit a route in the heart of O and/ or drawing areas with the OD plugin.
There are two ways to create and/or modify the routes in the heart of O: The way "non-touch screen" and the way "Touch Screen ".
And when I want to create and/or modify a drawing area with OD, it two other operating mode.
And yet there is a lot of commonality between these two activities.

Obviously, since I can not program, I should probably shut up. But, know that I respect the work you do and the developers as Jongough.
That said, it seems that choose a only one operation mode for non-touch screens, touch panels, routes, areas would be a very good thing.

On a touch screen, clicking on a waypoint. This waypoint is selected and this results in a yellow circle around it. Then the finger is moved. When finished the move, you click on it again and the small yellow circle disappears.

By example :
On non-touch screens, I gladly accept that you do the same. We could :
- Click on a waypoint with the mouse (or the thinger). A yellow circle around the waypoint would appear.
- Move it with the mouse (or the finger)
- Re-click on it to "de-select".
And it would be good if this method is also used for points dividing areas OD plugin. And this, especially, the right click is not easy to use with touch screens.

You can also choose to use the method of Jongough in the heart of O and so, again, harmonize all operations.

Best regards. Gilletarom.

[cagney]

Originally Posted by bdbcat

@cagney...

re:
Today I was "forced" to install 1301 on a Windows 10 laptop.
I found that "simplified" was indeed ticked by default.
Why are there different defaults on win and lin?
Is that due to the Win install script?
/Thomas

I cannot reproduce this. The defaults for this value are not set by the install script, but by empty config file on first run. You will see that on a very fresh install, there should be no config file at all until O is run for the first time.


What happens (on Windows) if you delete or rename the config file and start O from scratch?

Thanks
Dave

Dave
As expected, "Paper Chart" was selected.
Let's wait and see if you get more reports about "simplified".
Thanks
Thomas

[cagney]

Originally Posted by rgleason

Ah Thomas, you are here!
I need some help understanding how things work with the documentation..
I was going to ask Bdbcat about this outline and ask some other questions...

How does this look for the Main Outline?
Opencpn 4.1.1108 Documentation - Page 4 - Cruisers & Sailing Forums

If you and wdkester can review and make suggestions for changes, I can then go through all the docs and make sure the links are working properly. Is there a way I can do search and replace on the documents?, or at least I can use Find...?

Also I need to understand this which I found somewhere...
Opencpn 4.1.1108 Documentation - Page 4 - Cruisers & Sailing Forums



Also how is export done and can I try that to see how it works and if everything is working?

Thanks

Rick
Not quite....
Very limited connections, so I'm afraid I can't do all you would like me to do, for the moment.

Export, go to Download OpenCPN | Official OpenCPN Homepage scroll down to "Live Snapshot". This is basically the "final" documentation. For links to work internally i this document the names of the links must match the headings in the wiki for each page, to the letter. Just check out how it's done now. This is all down to a php script that Will wrote (and that I've never seen). This may lead to some, sometimes awkward, workarounds to make the writing understandable.

Thomas

[rgleason]

Thankyou Thomas. This is going to help I think.

So the names of the links (this is the url we type at the bottom of the editor page in view mode) must match exactly the Heading that appears in the menu to the left, which is controlled when in page edit mode by what is entered in the top line Title of the page.

Ok, we will have to check every pages formatting for the URL at the bottom MUST match the Title of the page exactly.

Also we are going to have to double check every link again. Not good news.

What I suggest is
1. Get the outline right.
2. Get the Page Titles clear and agreed to.
3. Change the URLs to match the Titles.
4. Check every link in all pages and paste in the proper one.

The last to steps can be done towards the end, but I think we should be changing the URL to match the TITLES as we work.
This will cause links in the docs to break until we get to fixing them yet again. This is a bit backwards, and maybe clever... but now I remember the problem from before!

Plus there is editing and updateing changes!

[rgleason]

And ptulp

[ptulp]

Rick,

It is not the link that has to match, but the text of the link as used in the document. I don't know if this is clear.
Most of the text is OK, just a very few problems.

Peter