OpenCPN Beta Version 3.3.1419 Released

[bdbcat]

Thomas...

Thanks for quick testing.

I tried to avoid nagging more than once in a particular session.

re:

Should we cover a case where there is a serial connection defined, but  the user doesn’t  belong to the correct group? This could be done when  starting O.

This case should be covered. See chart1.cpp, line 2426. It should nag once if there is an attempt to use a previously configured serial port.

Popup language OK?

Dave

[cagney]

Originally Posted by bdbcat

Thomas...

Thanks for quick testing.

I tried to avoid nagging more than once in a particular session.

re:

Should we cover a case where there is a serial connection defined, but  the user doesn’t  belong to the correct group? This could be done when  starting O.

This case should be covered. See chart1.cpp, line 2426. It should nag once if there is an attempt to use a previously configured serial port.

Popup language OK?

Dave

Dave
Yes, correct. As long as the serial connection is enabled, there is a warning when starting O, if the user does not belong to the right group.
If there is a previously configured serial connection, that is not enabled, no warning is given if the user tries to enable it. No big deal, we have to stop somewhere.

The Popup language is OK with me.

I have to backtrack what I said about the need to log out on Ubuntu, for the group change to take effect.
Changes of groups for a user takes effect instantly, but the "groups" command needs a renewed login to show correct values.

Thomas

[CarCode]

On Mac OS X Mavericks the syslog is filled with with several lines this:

02.03.14  10:58:07,986 OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name "Lucida Grande" and got font with  PostScript name "LucidaGrande". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:07,987 OpenCPN[386]: CoreText performance note: Set a breakpoint on CTFontLogSuboptimalRequest to debug.
02.03.14  10:58:07,989 OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name "Lucida Grande" and got font with  PostScript name "LucidaGrande". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:09,474  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name "Times" and got font with PostScript  name "Times-Roman". For best performance, only use PostScript names when  calling this API.
02.03.14 10:58:09,493 OpenCPN[386]: CoreText  performance note: Client called CTFontCreateWithName() using name  "Times" and got font with PostScript name "Times-Roman". For best  performance, only use PostScript names when calling this API.
02.03.14  10:58:09,506 OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name "Lucida Grande" and got font with  PostScript name "LucidaGrande". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:09,806  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name "Times" and got font with PostScript  name "Times-Roman". For best performance, only use PostScript names when  calling this API.
02.03.14 10:58:09,822 OpenCPN[386]: CoreText  performance note: Client called CTFontCreateWithName() using name  "Times" and got font with PostScript name "Times-Roman". For best  performance, only use PostScript names when calling this API.
02.03.14  10:58:10,812 OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name "Lucida Grande" and got font with  PostScript name "LucidaGrande". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:11,942  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name "Lucida Grande" and got font with  PostScript name "LucidaGrande". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:12,045  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name "Arial" and got font with PostScript  name "ArialMT". For best performance, only use PostScript names when  calling this API.
02.03.14 10:58:19,186 OpenCPN[386]: CoreText  performance note: Client called CTFontCreateWithName() using name  "Lucida Grande" and got font with PostScript name "LucidaGrande". For  best performance, only use PostScript names when calling this API.
02.03.14  10:58:19,435 OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,441  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,444  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,448  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,452  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,456  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,460  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,464  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,469  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,474  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,478  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,483  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,487  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,492  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
02.03.14 10:58:19,497  OpenCPN[386]: CoreText performance note: Client called  CTFontCreateWithName() using name ".Lucida Grande UI" and got font with  PostScript name ".LucidaGrandeUI". For best performance, only use  PostScript names when calling this API.
...

Reason is wxWidgets which does not handle this changes of font names in Mavericks.
In the latest commit of wxWidgets v3.1.0 from yesterday this is partly solved only:

using  a lazy translation hash map for conversion between user friendly names  and postscript names, so that we get only one warning per font family.  The only way to completely get rid of this would be to pre-populate the  map during startup which would mean to completely iterate through all  installed fonts, so it's a compromise. see #15999

After all we can (must) live with one line in the syslog.

Gerhard

BTW not only OpenCPN is affected but also any other application done with wxWidgets as e.g. PoEdit.app for OS X.

[JONA]

Hi,

The popup for "dialout" groupe works great on FC20 .The text is ok too.
Wind history text is also working.
MWD should work for Wind History now, I will test that in few days when i will be onboard.
Thanks Dave

Gilles

[alsobrsp]

I may have found an issue with the grib display. These two screen caps show the same file. It looks like the wave overlay is inverted.

[alsobrsp]

The overlays seem to be inverted for all.

[yachtvalhalla]

Originally Posted by alsobrsp

The overlays seem to be inverted for all.

I don't know if this is applicable but MaxSea will invert the latitude of gribs not obtained from their source.

Hence, in Airmail/Sailmail there is a capability to invert the latitude if using MaxSea when requesting grib files.



Terry

[alsobrsp]

I narrowed down the commit that introduced the issue.

Works:127a6f9e239285d0166d149a84873ca61e15a938
Broken: d9421cf3aff8d2da02cff94db2e39f8386c0cc8a

[bdbcat]

alsobrsp....

I think I see the problem. I need to test it.

Will you post your GRIB file, or the saildocs query request email contents?

Thanks
Dave

[alsobrsp]

Originally Posted by bdbcat

Will you post your GRIB file, or the saildocs query request email contents?

Here you go

send GFS:33N,23N,91W,72W|0.5,0.5|0,3,6..192|=
WIND,PRESS,APCP,TCDC,AIRTMP,HTSGW,WVPER,WVDIR,SEAT MP,CAPE

[bdbcat]

alsobrsp...

OK, thanks, got it.
Fixed the bug, and checks out OK for me.

You may pull and build the latest github source to try, if you like.

Thanks
Dave

[alsobrsp]

Originally Posted by bdbcat

You may pull and build the latest github source to try, if you like.

Looks great. Thank you

[fgd3]

I'm running OpenCPN on Windows Vista, using RNC charts. It has been a long time since I turned off chart quilting. I seem to recall OpenCPN used to automatically open an adjacent chart when quilting was disabled and I clicked into the new chart area. Now it doesn't seem to do that. Does anyone else experience that? Is it suppose to work that way?

Running on Ubuntu 12.04, 64 bit, the program does switch to the adjacent chart after a one or two second delay.

Fabbian

[cagney]

Originally Posted by fgd3

I'm running OpenCPN on Windows Vista, using RNC charts. It has been a long time since I turned off chart quilting. I seem to recall OpenCPN used to automatically open an adjacent chart when quilting was disabled and I clicked into the new chart area. Now it doesn't seem to do that. Does anyone else experience that? Is it suppose to work that way?

Running on Ubuntu 12.04, 64 bit, the program does switch to the adjacent chart after a one or two second delay.

Fabbian

Yes it is suppose to work that way. The change how single-mode works, took place a few years back. As quilting developed it became the mode that everyone was using, and the need for the old style single mode, more or less disappeared. One reason behind the change, was the desire to be able to read all the information on a raster chart, even the info that is outside the chart proper.

From the wiki

Single Chart Mode is the default display mode. In this mode only one chart at a time will be displayed. All the information printed outside the chart proper can be read. To change to another chart, select and click in the Chart Selection Bar. Read more in Status Bar. The other display mode is Chart Quilting.

There is no difference between Windows and Linux.

Thomas

[fgd3]

Originally Posted by cagney

Yes it is suppose to work that way. The change how single-mode works, took place a few years back. As quilting developed it became the mode that everyone was using, and the need for the old style single mode, more or less disappeared. One reason behind the change, was the desire to be able to read all the information on a raster chart, even the info that is outside the chart proper.

Thanks. I do remember that in the old days I had a problem reading information at the margins. Quilting--when it's working right--is better than single chart mode with automatic switching, but I turned it off to explore a problem I've had with northern Tampa Bay.

Originally Posted by cagney

There is no difference between Windows and Linux.

Thomas

Perhaps it is intended that way, but in fact there is a difference between Windows and Linux. With quilting not enabled when I click off the edge of a RNC on my Linux machine the adjacent chart opens after a second or so. That doesn't happen on my Windows Vista or Windows 8 computers.

Could there be a toolbox setting responsible for the difference? I think I have everything set the same on both systems.

I came across this while tinkering with a problem I've had with the Tampa Bay charts. The 11416 chart (Tampa Bay, Northern Section) uses an inset to show soundings around Safety Harbor. On my Windows computers, with quilting enabled, the soundings stop just north of the Courtney Campbell Causeway where the 11416 chart ends and the 11412 (Tampa Bay and St. Joseph Sound) takes over. In order to see the 11416_4 inset (Safety Harbor) I have to click inside the 11416_4 area, then manually select that chart from the status bar. The Linux version automatically shows the 11416_4 inset when I click in its area.

I first raised this issue in "Incorrect Displayed on Quilted Screen" but the discussion died out without a resolution. Here's a quote of the initial post if you want to review the thread.

Originally Posted by fgd3

I'm running Windows Vista, 7, and 8 on three different computers. I've installed OpenCPN 3.3.1117 on all three. With quilting on I get this odd situation. Around 27 degrees, 59.7046 minutes north, 082 degrees, 39.3028 minutes west using NOAA RNCs I don't see any soundings in the Safety Harbor-Mobbly Bay area (north of 27 degrees 58.5934 minutes north). The area is covered by 11416, Tampa Bay Northern Section and 11412, Tampa Bay and St. Joseph Sound. Only when I turn off quilting (F9) do I see the sounding and other detail for the area in question, which is shown on an inset, 11416_4.KAP. Shouldn't insets be shown on top of the base chart so that the maximum detail is visible?

Fabbian

Fabbian