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.
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?