Skip to content

WSJT-CB V1.3.0

Latest
Latest

Choose a tag to compare

View all tags
@BarceP BarceP released this 20 Jun 18:15
WSJT-CB-1.3.0
b881291

WSJT-CB 1.3.0

Version 1.3 introduces a visual restyling of the application and consolidates several technical aspects related to identity, configuration, and packaging.

Interface and theme

  • New modern dark theme, enabled by default at startup.
  • New unified visual system: palette, buttons, input fields, menus, tabs, tables, and scrollbars consistent throughout the application.
  • Improved main window chrome: decode panels, headings, borders, and splitters are now more consistent.
  • Main window dimensions updated for better rendering on current desktop setups.

Identity and configuration

  • Project versioning updated from 1.2.0 to 1.3.0 across the repository.
  • Titlebar/branding signature updated to 1AT106 1XZ732 1AT1989.
  • Settings storage now uses a stable base name (WSJT-CB.ini) and automatically migrates old .ini files tied to the previous branding: changing the titlebar branding no longer resets user settings.
  • The default logging directory is now also stable, and logs from the previous version are migrated automatically.
  • The worked-before logbook and country lookup now use the stable writable data directory, so wsjtcb_log.adi, cty.dat, and grid.dat stay aligned with the directory opened from the UI.

CAT and Windows packaging

  • Restored OmniRig support on Windows (WSJT_WITH_OMNIRIG, generated with Qt ActiveQt/dumpcpp or dumpcpp-qt5), available again as OmniRig Rig 1 / Rig 2 in the transceiver list.
  • The Windows/MSYS2 build now compiles and packages against Hamlib 4.x (verified with Hamlib 4.7.2~rc on UCRT64); the installer includes the required Hamlib runtime DLLs.
  • Added a repeatable Windows packaging script for the 1.3 build: it configures CMake/Ninja for UCRT64, enables OmniRig, stages dist, copies the required runtime DLLs, verifies dependencies, and creates the Inno Setup installer.

Validation and CB QSO handling

  • Validation of the "My callsign" field is now CB-specific: it must match the WSJT-CB CB callsign format (e.g. N{1,3}L{1,2}N{1,3} or N{1,3}L{1,2}/LL); invalid/non-CB values are highlighted in red and the configuration cannot be saved until they are corrected.
  • Automatic CQ/QSO handling now starts QSOs only with complete CB callsigns: non-standard, non-CB, incomplete, or unresolved hashed replies remain visible in the received messages but are ignored by AutoSeq, so CQ operation continues normally. Directed free-text replies that clearly match our callsign are still handled as valid QSO progress.

First RPM release.

  • To be considered beta, any feedback is appreciated
Assets 7
Loading