AntScopeZ 2.2.5 (Windows beta)

Windows beta build of AntScopeZ 2.2.5. Native Windows support (NSIS installer, taskbar/Start-menu icon) plus a batch of fixes from live UI testing on real NanoVNA hardware.

Added

• Native Windows support: builds and runs natively on Windows (Qt 6.11.2, MinGW), packaged as this NSIS installer.
• File > "Disconnect Analyzer" menu action, next to Connect Analyzer.
• Settings > Themes: an Apply button to activate the selected theme immediately.
• About dialog: credits K4HEZ (creator) and KC5CD, with a link to RigExpert's AntScope2.
• -developer-gated CLI flags (-comserial/-usbhid/-nanovna/-ble) to enable Debug Logging at launch.

Changed

• NanoVNA: no longer hard-locked to 100 scan points -- uses the same configurable points field/slider as every other analyzer.
• Band Selector now defaults to enabled at startup (a deliberate stopgap while the real cross-restart configuration behavior is decided).
• Analyzer connections: consolidated "device busy" and scan-timeout-watchdog handling across HID, Serial, and NanoVNA connections into shared logic.

Fixed

• Windows: taskbar/Start-menu icon was missing; now shows correctly.
• Amateur band definitions: 60m corrected in all three ITU regions (US: 5 channelized lines instead of one inaccurate wide range; IARU: 5351.5-5366.5kHz), and the previously-missing 33cm band added for Region 2 (US/Canada). Also fixed a 70cm/23cm label typo in Region 1/3.
• Band preset dropdown wasn't updating the S21 chart's X-axis range along with every other chart.
• TDR: a NanoVNA TDR scan left the dialog's controls disabled after one measurement, with no way to change settings or re-scan without closing the dialog.
• Smith chart: the cursor position dot stayed at its last position instead of resetting on a new scan or Clear.
• Start/Stop frequency fields didn't apply their value when clicking elsewhere; also fixed a duplicate-connection bug that ran the update logic twice per edit.
• NanoVNA: fixed a 0Hz first point and a race on the first Single-click right after connecting.
• Various NanoVNA edge cases: leftover S-parameter points after Stop, marker auto-placement using stale data after an empty/cancelled scan, a binary-scan-mismatch error skipping cleanup, and a stale-row bug in the device selection dialog's Connect button.
• SWR chart: vertical click-drag disabled (only Ctrl+scroll zooms the Y axis).
• Installer: fixed a missing ftd2xx.dll and a broken ProgramData data-file path.

Full detail: CHANGELOG.md

🤖 Generated with Claude Code

v2.2.5-win64-rc

[2.2.5] - 2026-09-07

Changed

• File > "Data from AA" moved to the Analyzer menu, under "Screenshot...".
• Settings > Analyzer: "Use reconnect to drain unwanted data" moved from
  the General tab, placed under "Analyzer timeout:".
• Settings > Analyzer > Custom Analyzer: "Use customized analyzer"
  checkbox moved out of the group box to directly above it, and now
  enables/disables every control inside. The "under development" label
  and the group box's permanent forced-disable are gone -- Custom
  Analyzer is a live feature now, no longer gated behind the (removed)
  -developer flag, and its on/off state and saved presets persist
  across restarts.
• Spin boxes, combo boxes, and sliders throughout the app no longer
  react to the mouse wheel unless already focused (click or Tab in
  first) -- fixes values silently changing while scrolling past a
  control on a long settings page.
• Settings dialog: labels/fields grid-aligned and oversized/mis-sized
  text boxes fixed across General, Markers, Analyzer, and Graphs tabs
  (several fields were stretching to fill the dialog width, or sitting
  far from their label, instead of sizing to their actual content).
• Settings > Graphs > "Chart Y-Axis Ranges" reworked into a 3-column
  grid (chart name | min | max) instead of 4 separate min/max-labeled
  rows.
• "Edit ITU Bands..." moved off its own Edit menu (now removed) onto a
  new Settings > ITU Bands tab, between Graphs and Updates -- same
  text box and Cancel/Restore Defaults/Save buttons, just living on a
  tab instead of a standalone dialog. The Analyzer menu now sits where
  Edit used to (right after File).

Fixed

• Custom Analyzer: AnalyzerPro::getMinFq()/getMaxFq() returned a
  model-name string instead of a frequency (copy-paste bug); had no live
  caller, so no observed symptom.
• Settings > Custom Analyzer's "New" button set the prototype combo box
  to the literal text "names[0]" instead of selecting a real entry.
• Pressing Esc in the Settings dialog closed it but left File >
  Settings... permanently disabled -- a latent bug present since this
  fork's first commit, never previously exercised/reported. reject()
  (Esc's actual entry point) now routes through the same cleanup the
  Close button already used correctly.
• Band Selector: dropped the issue #23 stopgap that force-enabled it on
  every startup regardless of what was saved -- it's a plain persisted
  bool again (default true only when unset), so turning it off
  actually survives a restart now (#13).
• View > Band Highlighting had no region checked on first launch (or
  after deleting the ini) even though bands were correctly shown --
  the menu-builder and every other reader of the same current_band
  ini key disagreed on its default. Both now go through one shared,
  self-healing resolver that also persists its choice immediately.
• Editing bands in Settings' ITU Bands tab and clicking Save now
  rebuilds the View > Band Highlighting menu immediately instead of
  requiring a restart to see a renamed/added/removed region.
• Charts (and printed output) no longer fall back to a hardcoded
  18-entry ham-band list when the current region has no band data --
  they draw nothing, matching an intentionally-empty itu-regions.txt.
  Also fixes itu-regions.txt/Settings' ITU Bands tab edits not
  clearing already-drawn bands when the new region has none.
• Ported 3 Smith-chart fixes from RigExpert AntScope2 2.0.3 that never
  made it across the QCustomPlot 1.x->2.x rewrite (#10): point
  indexing that diverged across a Continuous "continue" (could corrupt
  point ordering); the Smith trace losing its assigned color on every
  "continue" (pen never reapplied after the curve was recreated); an
  out-of-range crash risk hovering the Smith chart cursor (a bounds
  clamp was already written in the code but commented out).
• Measurements::saveData() silently did nothing (no file, no
  warning) if the save path didn't contain ".asd" -- not guaranteed,
  since the file dialog never calls setDefaultSuffix(). Appends the
  extension instead of refusing to save (also from AntScope2 2.0.3, #10).
• BLE analyzer: writing a new command (start scan, screenshot, get
  analyzer data) while a ping response or another transfer was still
  outstanding risked colliding with it on the wire. New commands now
  queue and dispatch once the outstanding one actually completes;
  Stop now sends a real wire abort too (still treated as best-effort,
  not guaranteed) instead of only a local flag. Ported from RigExpert
  AntScope2 2.0.3, #10.
• Follow-up to the BLE queueing fix above: the Screenshot dialog's
  completion never actually reached the BLE analyzer at all
  (AnalyzerPro::on_screenshotComplete() was missing the call), so its
  queueing state could stay stuck after a screenshot; a per-record
  reset in the analyzer-data list fetch could clear it mid-fetch
  instead of only once the whole list was done; FULLINFO's last field
  and an empty-queue ping response weren't resetting it either.
• License tier "BASE"'s max frequency was still 70MHz; RigExpert
  AntScope2 2.0.3 corrected it to 75MHz.
• AA-650 ZOOM screenshots: the device can report a different pixel-
  compression mode over BLE (FULLINFO's screenCompression field);
  Screenshot only ever decoded the one format, so screenshots came
  out wrong/garbled on the other mode. Now picks the right decode
  based on what the device actually reports. Ported from RigExpert
  AntScope2 2.0.3, #10.

Removed

• The -developer CLI flag and g_developerMode, along with the
  -comserial/-usbhid/-nanovna/-ble CLI shortcut for pre-enabling
  Debug Logging -- both already inert/redundant (Debug Logging is always
  reachable via Settings > Developer's checkboxes regardless). The
  already-deleted UDP remote-control bridge's leftover documentation in
  BUILDINFO.md was trimmed to match.
• The standalone "Edit ITU Bands..." dialog (EditBandsDialog) -- its
  functionality now lives on Settings' new ITU Bands tab instead.

Documentation

• Ran update_translations and translated this cycle's 14 new/changed
  source strings (Settings' reworked General/Analyzer/Graphs tabs, the
  new ITU Bands tab, and the About box's updated text) for Ukrainian,
  Japanese, and Spanish. All 3 .ts files are 765/765 finished, 0
  unfinished.
• User Guide, roadmap, and BUILDINFO.md updated to match this cycle's
  menu/Settings reorg (Data from AA's new home, General/Analyzer tabs'
  actual current contents, Custom Analyzer no longer described as
  disabled/under development) and to reflect the Windows port merge
  (build/deploy verified working; real-hardware verification still
  outstanding -- see docs/windows-port-audit.md).

Full Changelog: v2.2.5-win64-beta...v2.2.5-win64-rc

AntScopeZ 2.2.2 -- Windows beta

First native Windows build of AntScopeZ, built with MinGW 13.1.0 / Qt 6.11.2 (windows-port branch, commit cfbf93f).

What's in this build: everything from the 2.2.2 Linux release, running natively on Windows. Qt DLLs and required plugins (platform, TLS/Schannel, image formats) are bundled -- just unzip and run AntScopeZ.exe.

Status: beta, hardware-unverified. The app builds cleanly and launches, but device-facing paths (hidapi/USB-HID, FTDI serial, Bluetooth, the .asd file association, device-change detection) have not yet been exercised against real RigExpert hardware on Windows. See docs/windows-port-audit.md on the windows-port branch for the full porting audit and open items.

Package: AntScopeZ-2.2.2-win64-beta.zip -- extract anywhere and run bin\AntScopeZ.exe.