OpenCPN Version 2.4 Beta Build 310

[cagney]

Dave
Aha. This could be related to what I found when testing the offsets.
See my comment on FS #308.
Thomas

[HotRod]

I got some weird artifacts after updating to the beta.
Using CM93 dated 2010.
The artifacts come and go, and are not consistent.

See the enclosed pictures.
One with artifacts and one without.

Any ideas?

[PjotrC]

Dave,

Windows Vista, installs & compiles fine.

1. The problem reported by janp391 easily reproduced.

2. I noticed a strange error message in the logfile (marked in bold):

6:01:35 PM: PlugInManager: Deactivating PlugIn: E:\Dokumenty\charting\opencpn_240\OpenCPN\plugins/dashboard_pi.dll
6:01:35 PM: PlugInManager: Deactivating PlugIn: E:\Dokumenty\charting\opencpn_240\OpenCPN\plugins/grib_pi.dll
6:01:35 PM: opencpn::MyFrame exiting cleanly.
6:01:35 PM: Error: can't open file '' (error 0: operacja ukonczona pomyslnie.)
6:01:36 PM: PlugInManager: UnLoading PlugIn: E:\Dokumenty\charting\opencpn_240\OpenCPN\plugins/dashboard_pi.dll
6:01:36 PM: PlugInManager: UnLoading PlugIn: E:\Dokumenty\charting\opencpn_240\OpenCPN\plugins/grib_pi.dll
6:01:36 PM: LOGBOOK:  2011-03-14 17:01:36 UTC OFF: Lat   55.37090 Lon   17.46500
6:01:36 PM: opencpn::MyApp exiting cleanly...

The comment says "error 0: operation successful". This occurs most of the time, but not always, both in the installed distribution and my local build.

3. When quilting CM93 charts the ENC text is sometimes rendered incorrectly (sample attached).

4. Not a bug, but just a thought: perhaps manual changes to chart offsets should be recorded in a log for easier replay/sharing etc.?

5. In my local build of OCPN I cannot get the plugins to be visible. They are visible and work when running the PACKAGE build (the build process breaks because of invalid comments in "project.nsi", but the executables run fine)

6. The git-magic is incredible... I merged my projects from 2.3.1 with just one easy manual conflict...

Thanks for all the work,

Piotr

[bvimatelot]

Still havent sorted out that Garmin support yet? T

[nohal]

Originally Posted by PjotrC

5. In my local build of OCPN I cannot get the plugins to be visible. They are visible and work when running the PACKAGE build (the build process breaks because of invalid comments in "project.nsi", but the executables run fine)

Piotr...
Don't know if I understand correctly what your problem is, but if you want to debug plugins, you have to either
- add a postbuild step to copy them to a location where the debug build of opencpn looks for them
- temporarily change line 109 in pluginmanager.cpp to something like

m_plugin_location = _T("C:\\WORK\\opencpn\\source\\opencpn\\build\\plugins\\gecomapi_pi\\Debug");

I somehow prefer the second option as I can throw away the whole build directory and regenerate it with cmake whenever I want

Pavel

[PjotrC]

Pavel,

I make Release compilations only and I think I have moved the plugin .dlls into the right directories. I had the same with 2.3.1. Will keep looking....

Thanks,

Piotr

[nohal]

Then hard to say, for release build try to place some wxLogMessage stuff around that place in pluginmanager.cpp and you should find out whether the problem is the placement or a problem in loading the dlls...

[HappySeagull]

HAPPY to have my old Polyconics,Transverse Mercator (" UTM" too) back aboard!
Thanks! I'm sure I'm not the only one with these!
...I sort of miss the old verbose log as it commented on each and every chart but I'll get over it.nd maybe I'll poke OpenCPN 2.4 with a fake kap and see if she'll bark...Oh Yes!She noted it plainday.with all the others.Good oh!

[cagney]

The Dashboard has come a long way in a short time thanks to SethDart's efforts, see Daves #10 & #11above.
What is not so obvious is that even horizontal docking is now supported, even docking with another dashboard is OK.
Dashboards are now either vertical or horizontal, but this is not set in stone and can be changed. There are a lot of options here to explore.



Thomas

[CarCode]

Thomas,
one of the most needed options for Dashboard is to make its window transparent and not to make the chart screen smaller and smaller as seen in your example. Think for the users please.

Gerhard

[SethDart]

Hi Gerhard,

I wanted (semi) transparent pane from the begining but it's not (yet) available in wxWidgets. Remember, we're using this multi-platform library for all the frames, buttons, dialogs, etc. thus we rely on its features. I tried wxWindow::SetTransparent but nothing changed. but only tested on Linux/GTK, maybe Windows / MacOS works?
You can try and report results, add
SetTransparent(128);
in plugins/dashboard_pi/src/dashboard_pi.cpp:1667

PS: I noticed in another message from you that you were disapointed with new dashboard interface. Please elaborate, be constructive: send drawings, mockups or any idea that would help. I'm not a designer.

We should continue this discussion here:
http://www.cruisersforum.com/forums/...ard-44087.html

[nohal]

Jean Eudes,
I've read somewhere that SetTransparent() works on Win and MacOS (and not on Linux at least if your X server doesn't have the composite extension loaded and you are not running a compositing manager), that's why there is CanSetTransparent(). Will try it on Win and let you know... For floating frames the solution would be easy.

Pavel

[CarCode]

Pavel,

please try the "shaped" sample which is part of the shipped wxWidgets distribution. Does it work with your configuration?

SethDart,

I have wrote into the Dashboard thread http://www.cruisersforum.com/forums/...ard-44087.html

Gerhard

[PjotrC]

For routepoints shared between multiple routes (e.g. by affirmative answer to "Use nearby waypoint?") this property seems to no longer keep after program restart or route export/import. Is this the intended behaviour?

[nohal]

Piotr,
the current behavior is the result of FS#349 patch - it's the best logic I was able to come with... Which of course doesn't mean it has to be right.
Could you elaborate a little bit about the after-restart behavior you don't like? I don't see a problem there at least as far as I understand the desirable workflow.

Pavel