leamas

> f I'm correct the fix would be to show this option only when O is started as described above? Or dismantle it? Or fix it so it writes on...

This is not a bug in wxVector. It has been discussed in [zulip](https://leamas.github.io/zulip-archive/stream/332168-Master---5.2E8.2E0--.28was.3A-comms.29/topic/Windows.20build.20broken.html)

The same is probably true for the dialogs presented for missing device permissions on Linux. However, this is less likely to happen in a correctly configured environment.

@svMigration The beta is out. Could you possibly test it to check that the issue indeed is gone? Info on installing the beta [here]( https://www.cruisersforum.com/forums/f134/opencpn-v5-9-1-beta-test-starts-286845.html)

Yes. But using that would mean that in the headless case a user which connects later will not see this quite important message. It would also mean a long delay...

IMHO, we should add a unit test here. It's easy to test, and having it in the test suite handles regressions. Might be able to do this later.

hm... can't sleep, digging a little. The need to truncate the waypoint name is obvious for RMB messages when they become too long. However, is decreasing `g_maxWPNameLength` the right to...

Seems like none of us are really sure here. In that situation I think it might be better to just fix RMB messages for two reasons. The first is that...

One more thing: Auto-generated waypoints typically has names like W00001, W00002, etc. truncating these is then certain to create duplicate names. Would it be better to strip the prefix in...

Here, untested: ``` // RMB { int wp_len = maxName; SENTENCE snt; do { snt = SENTENCE(); m_NMEA0183.TalkerID = "EC"; m_NMEA0183.Rmb.IsDataValid = bGPSValid ? NTrue : NFalse; m_NMEA0183.Rmb.FAAModeIndicator = bGPSValid...