OpenCPN Version 4.2 Released

[svcattales]

I seem to be missing the capability to move waypoints on existing routes. In previous versions I could left click on a waypoint and move it to a new location. Moving waypoints is often necessary when you realize that the route you just built passes over a shoal that you didn't see until you zoom in. I can use the "insert waypoint" function but I'm limited to inserting it along the route and can't use it to shift the route in any direction. Now I would need to rebuild the entire route to fix one mistake.

Anyone else experiencing this issue? I'm using Win 8.1 with open GL selected on ocpn 4.2. All other functions and plugins are doing just fine.

[nohal]

Greg...
Probably nobody because this issue likely does not exist. Make sure "Lock waypoints" is NOT checked on Display -> Advanced tab in the toolbox.

Pavel

[petter5]

Originally Posted by svcattales

I seem to be missing the capability to move waypoints on existing routes. In previous versions I could left click on a waypoint and move it to a new location. Moving waypoints is often necessary when you realize that the route you just built passes over a shoal that you didn't see until you zoom in. I can use the "insert waypoint" function but I'm limited to inserting it along the route and can't use it to shift the route in any direction. Now I would need to rebuild the entire route to fix one mistake.

Anyone else experiencing this issue? I'm using Win 8.1 with open GL selected on ocpn 4.2. All other functions and plugins are doing just fine.

Under Linux - Opencpn 4.2 I'm able just to grab the waypoint with the mouse and move it. Just made a route and tested this function.

[Gilletarom]

W 8.1. O 4.2

I confirm that there is no problem. Easy to move waypoint with mouse.

[seandepagnier]

Originally Posted by nohal

J-P...
Buildwin is not having the binary blobs purposedly, not to inflate the git repository, you must populate it with the files from https://sourceforge.net/projects/ope...in.7z/download (There was an update to it about 2 months ago because of the new SVG support)

Pavel

The SVG support broke building using mingw which I use to detect many windows specific problems with my plugins. I will try to correct it.

Anyway... why can't the cmake script invoke wget to pull this and extract it automatically as part of the build process?

[nohal]

Originally Posted by boat_alexandra

Anyway... why can't the cmake script invoke wget to pull this and extract it automatically as part of the build process?

Because there is no wget on Windows. But feel free to implement it if you think it's time well spent. I don't.

You can sure build with the SVG support disabled on MingW.

Pavel

[svcattales]

Originally Posted by nohal

Greg...
Probably nobody because this issue likely does not exist. Make sure "Lock waypoints" is NOT checked on Display -> Advanced tab in the toolbox.

Pavel

Thank you very much, Pavel. I had some issues overlaying 4.2 on 4.0 and ended up doing a new download. I missed that "lock waypoints" box when I configured all the settings. It works great now!

[dwoodall]

FWIW there is a Windows GNU Wget here https://www.gnu.org/software/wget/ and precompiled binary here https://eternallybored.org/misc/wget/. Never tried either and have no idea if they work properly.

Regards,
Doug

[nohal]

Originally Posted by dwoodall

FWIW there is a Windows GNU Wget here https://www.gnu.org/software/wget/ and precompiled binary here https://eternallybored.org/misc/wget/. Never tried either and have no idea if they work properly.

Regards,
Doug

They of course do, but they are not available without manually installing them = unusable for us to get rid of one manual step in the build process...

[transmitterdan]

Windows comes with built in toolset that provides same functionality as wget. Read about Windows PowerShell.

[nohal]

Dan...
Did you try to implement something in it? I did, will not repeat...

Pavel

[transmitterdan]

Yes, I created a set of scripts to pull from git and the buildwin repository, run all the cmake steps to create OpenCPN (release and debug) as well as move all plugins to the right place for debugging. Not that painful. Will be happy to share if there is interest.

[transmitterdan]

Pavel, thanks for fixing the need to run cmake twice [emoji3]

[rgleason]

Transmitter Dan:

Yes, I created a set of scripts to pull from git and the buildwin repository, run all the cmake steps to create OpenCPN (release and debug) as well as move all plugins to the right place for debugging. Not that painful. Will be happy to share if there is interest.

Dan, I have some .bat files from you earlier, which do much of this, but they are using git, cmake and xcopy.
build.bat
clean.bat
config.bat
dbuild.bat
dbcopy.bat
git_opencpn.bat
all dated about 10/15/2015
(also 2 of these bats may be from Hakan)

And in git_opencpn.bat there is a powershell command that works great

cd Opencpn
powershell -Command "(New-Object Net.WebClient).DownloadFile('http://sourceforge.net/projects/opencpnplugins/files/opencpn_packaging_data/OpenCPN_buildwin.7z/download', 'OpenCPN_buildwin.7z')"
7z x -y OpenCPN_buildwin.7z

I have modified some of these for plugins too, and now have a clean-build bat file that will clean out the build directory of all typical files and directories except opencpn.lib and build.bat and any special non-standard files that are left. I still have to delete the directory [plugin]_pi.dir (which can be easily added).

However using the powershell command in a plugin command, you could just delete the whole build directory everytime and just rebuild it, which might be better.

Yes, I would be interested. I am sure I am not using the bat files to potential, but cleaning up the 50 or so plugin gits the batch techniques came in handy.
Best
Rick

[yachtvalhalla]

Originally Posted by svcattales

Thank you very much, Pavel. I had some issues overlaying 4.2 on 4.0 and ended up doing a new download. I missed that "lock waypoints" box when I configured all the settings. It works great now!

A word of caution. When waypoints are not locked there is the danger of accidentally moving a waypoint in a route and not noticing it. A better way is to keep waypoints locked. But if you right-click on a waypoint you want to move, select 'Properties' and while the Properties window is displayed you can then move the waypoint. Closing the Properties window lock it again.

Terry