OpenCPN Version 2.6 Beta Build 1729

[JesperWe]

Originally Posted by bdbcat

Here for your review is the text for the OpenCPN Version 3.0 announcement. This is intended to read like a one-page Press Release.

Have a look and let me know asap if I have missed any points or features that should be mentioned more prominently.

My suggestion would be to end with a URL to the extended release notes at OpenCPN 3.0 release notes. | Official OpenCPN Homepage, they are quite nice by now. (provided that you put in a nice first paragraph on that page, same text as the one above maybe).

[bdbcat]

Jesperwe....

That's the plan. When we finalize the Release Notice, we can place it verbatim in the extended Release Notes, and cross reference.

Thanks
Dave

[hwecken]

Originally Posted by bdbcat

...
OpenCPN Version 3.0 is released, and available for immediate download.
...

Download OpenCPN Version 3.0 at
OpenCPN | Free Science & Engineering software downloads at SourceForge.net
...

where to find the download to V3.0.
on the announced link i can only find V2.5 and earlier
vb Hartmut

[bcn]

Hartmut,

Dave refers to the proposed Release notes, so you can either download the 2.6.1729 - the latest release candidate - from the opencpn.org site or wait a little bit to find the 3.0 when released.

Hubert

[bcn]

Wouldn't it be interesting to list in the release note the existing plug-ins without going in details.
Those add a lot of very attractive features.

Hubert

[cagney]

Originally Posted by bdbcat

Thomas...

I agree that toolbox->etc->Show Layers Initially seems not to do anything useful.

Too late to do anything about it for 3.0, but we may ask "What should it do? Is it a global layers visibility toggle?"

Thanks
Dave

Dave

Nothing! Let it go and concentrate all Layers handling to the Route Managers Layers tab. A new button may be introduced there, if there is some user demand, "Show All/Hide All" , for a quick look at available layers.

Thomas

[Gilletarom]

Hello Dave,

Sorry, Late, Late ....

I have send a new version for french files language on OpenCPN Internationalization ( i18n )

B.R.
Gilletarom

[sinbad7]

Dave..

Found one of the tracks I was not able to erase.
It was an un-named short test track which had attached itself to my main BRAZIL-POI.gpx file. I found it by examin ing the entire file with an editor.

It happened while the main BRAZIL-POI.gpx file imported to the Waypoints area of the Route Manager was open.

Would it not be safer to refuse tracks to be saved without a name?

I still have that second land track (pink) I am unable to find and delete and have no idea where it is saved.

Tore

[bdbcat]

Tore...

That track must be in BRAZIL-POIS gpx file. Somewhere.

I'll try to reproduce the scenario.

Dave

[sinbad7]

Dave.

If you switch off/on the BRAZIL-POI.gpx link in the layers area of OCPN or in the Waypoints area after importing the file,the track is still there.
But I will keep looking.

Sorry to bother you with small things now you are busy finalizing v. 3

Tore

[sinbad7]

Found the last offending Brazilian land track in the W.Caribbean.gpx file and deleted it. Found also other unwanted tracks there which were deleted.

I think that there definately should be a way to avoid unnamed tracks to be accidentally included in any Waypoint file which happens to be open at the time.
Could that be ensured in a future version?

Tore

[sinbad7]

Unfortunately,the Brazilian land track still persists. I have looked EVERYWHERE,edited everfy file and deleted all navobj... files. Ideas anyone??

Tore

[JesperWe]

Originally Posted by sinbad7

Unfortunately,the Brazilian land track still persists. I have looked EVERYWHERE,edited everfy file and deleted all navobj... files. Ideas anyone??

Tore

Move all you .gpx's to somewhere wher OCPN doesn't see them, and put them back one by one, starting OCPN anew for each one. At least then you know which file it is in.
/j

[cagney]

Originally Posted by sinbad7

Found the last offending Brazilian land track in the W.Caribbean.gpx file and deleted it. Found also other unwanted tracks there which were deleted.

I think that there definately should be a way to avoid unnamed tracks to be accidentally included in any Waypoint file which happens to be open at the time.
Could that be ensured in a future version?

Tore

1 Don't ever import a gpx file in the layer folder as a gpx file. Layers are more permanent features, not made for quick fixes. Edit copies, located elsewhere, and update the layer when you are happy with the result.

2 If you have opened a layer as a gpx file, don't use "Export All..", because everything gpx related that is open will be exported. If you then save to the original layer, all bets are off, .... as you have seen.

3 If you want to ignore the first two points, make sure that absolutely no gpx related features, that you don't want to add to the layer, are open.

Thomas

[hoolie]

A couple of minor cosmetic glitches with 2.6.1729 :-

1) Tool box transparency doesn't work on XP SP3 or W7 if OpenGL is selected. OK on 2.5.0.

2) As reported earlier on this thread, the chart text size is very large after installation. I have had char size 26 point on 3 different machines. Easy to repair, but disconcerting for a novice user. I've not had this with any earlier versions.

Best of luck with version 3.0