hamlib problem fixes

[barjac]

This is the culmination of several days collaboration with Claude AI to investigate and test fixes for several klog hamlib related problems, some of which have been recurring on and off over several years:-

  Fix Hamlib auto-connect when window shown before init() (335e2626)
  Hamlib was not connecting automatically at startup if the Settings window was displayed
  before init() had completed. The auto-connect logic now runs correctly regardless of 
  window initialisation order.
  The status display is now updated correctly when the connection state changes.
  
  Fix rig_get_split_vfo causing VFO toggling on poll cycle (3309947d)
  Some Kenwood rigs (e.g. TS-450S) implement rig_get_split_vfo by physically switching VFOs
  as a side-effect, causing the radio to jump to a different band/frequency on every poll
  cycle(issue #947). 
  A probe runs once at connection time to detect this behaviour; if detected, split polling is    
  disabled for the session and the VFO is restored immediately.
  A secondary memory-channel guard skips the split query entirely when the radio is in memory
  mode, where the query has no meaningful result and the side-effect is most disruptive.
  
  Harden VFO probe and memory guard against rigctld contention (44b548aa)
  When KLog shares a rigctld instance with another application (e.g. FreeDV), two robustness
  problems were identified:
  - A single transient rig_get_vfo failure (rigctld busy) was permanently disabling VFO querying
  and clearing the cached VFO state, causing the memory-channel guard to never fire again.
  - The split probe only detected VFO side-effects via frequency comparison; if rig_get_freq
  failed due to contention the probe was inconclusive. The probe now also checks for a VFO state
  change, making detection reliable even when frequency reads fail.
  
  Fix Hamlib activation checkbox wrongly unchecked on NOK status (1531c07d)
  A transient NOK connection status at startup was unchecking and disabling the "Activate HamLib"
  checkbox. The OK path only re-enabled it, not re-checked it, so after a successful Test the
  checkbox remained unchecked and hamlib stayed disabled without the user realising.
  The checkbox now preserves the user's activation preference across transient connection failures.
  
  Fix Hamlib settings frequency display truncating to 3 decimal places (1ccc8325)
  The frequency shown in Settings → Hamlib was limited to 3 decimal places in MHz, rounding
  e.g. 5.3685 MHz to 5.369 MHz. The display now uses 4 decimal places.``
 

[sonarqubecloud]

Quality Gate passed

Issues
4 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud