OpenCPN Version 2.6 Beta Build 1705

[Ptizef]

Same problem with F5 and No GL mode as described above
Above patch correct it for me to (Vista)
thanks
Jean Pierre

[Ptizef]

Some texts are very far from the corresponding objects . (see screen dumps attached )
These examples are displayed from CM93_ed2_2009 and 2011 version
It's not knew , but if it could be improved ...
Thanks
Jean Pierre

[pa36651]

I sailed 20nm today with this beta on a XP SP3 old Lap with GPS and AIS connected via USB hub. Worked good!

[mrm]

Dave,

with regard to that I have a suggestion. Perhaps, instead of those messages let Open CPN continue, but make GPS status indicator clickable?

I imagine this would work like that: Open CPN starts but shows the icon for 'no GPS signal' in the GPS status indicator. When user wants to know why there is no signal, they can click the status indicator and then they will get a window with one or more messages telling what Open CPN thinks may be a problem (i.e. messages you refer to).

This idea could be extended to display a more generic clickable 'abnormal condition' icon. Something similar to what Android devices do, when they detect something abnormal or very important. They display a warning icon (triangle with an exclamation mark) and it is up to the user to see what it is about.

Marius

Originally Posted by bdbcat

Thomas, et al...

New behavior with NMEA source = libgps:

If you have NMEA Source set to network libgps, and you start OpenCPN without the gpsd daemon running, then you get an informational message dialog, viz:

Call to gps_open failed.
Is gpsd running?
gpsd host is:

You may start gpsd manually at any later time, and OCPN will detect the event and do the right thing. Or, on Ubuntu 12.04, gpsd is pre-configured to autostart on hotplug of a USB GPS receiver like Bu353. Again, OCPN will detect that and activate the interface.

Question: Is this "informational" dialog necessary, or is it a useless nag?

Similar question for Windows: The

"Could not open serial port 
Suggestion: Try closing other applications"

A useless nag?

Dave

[bdbcat]

Ptizef....

Regarding your #77 post about misplaced feature labels in cm93:

Unfortunately, the location of the label is coded in the chart as a _texto feature at a specific lat/lon, which may have nothing to do with the true location of the feature indicated. Thus, we cannot change the location of the text.
It is built-in to the chart database.

Sorry.
Dave