Fldigi v3.23.21 now available

The hard-working development team led by W1HKJ have announced the release of Fldigi v3.23.21.

This version of Fldigi is a maintenance release with a couple of bug fixes and several new features, including the addition of several new micro modes. Full details are available in the ReadMe file available for download and below this announcement.

As with all of the FL suite, Fldigi continues to support both PowerPC and Intel (i386) processors; with individual downloads available for each architecture and can be downloaded here.

Version 3.23.21 — Maintenance release

  • PSKMAIL beacon faults
    • investigate and correct seg faults caused by pskmail beacon
  • Documentation
    • corrections to browser doc page
  • kml auto_ptr deprecated
    • Change code to avoid C++11 warning regarding use
      of auto_ptr. Maintain backward compatability.
  • build flags
      – –param=max-vartrack-size=0
  • Logbook update
    • Too many reports of lost logbooks due to operator error
      – specifically selecting “New” should create a new log
      named “newlog.adi(f)” in the default logbook folder.
      – force the user to specifically request a write over /
      erase if the file already exists!
    • Save the following ADIF fields from their associated
      text edit field
      – <STATION_CALLSIGN> <== Station Call, existing
      – <OPERATOR> <== Operator Call, new
      – <MY_GRIDSQUARE> <== Station Locator,existing
      – <MY_CITY> <== Station QTH, existing
    • Change add a logbook entry to append rather than
      rewrite the entire log.
      – adding a new record only writes a single record
      to the h/d file. Reduces work load for older
      computers operating with marginal OS (read as XP)
      and support h/w.
    • Change cQsoDB sort routines to avoid copy of any
      records or record contents
      – references to pointer and pointer contents is always
      faster if not as safe
    • Removed CRC values in logbook data base file
      – unused and not needed
    • Update fldigi logbook documentation
  • N3FJP record rejections
    • Insure that CALL and other fields are stripped of
      leading and trailing whitespace before submitting
      log record to N3FJP application
    • Inhibit multiple dup checks on the same call sign
    • Inhibit dup checks on calls with less than 3 alpha-numeric
    • Inhibit dup check on calls with 3 alph-numeric when last
      char is numeric
    • Inhibit N3FJP refresh of CALL after submitting a log entry
      – fldigi was calling TABEVENT which in turn updated the
      CALL entry in fldigi … a bit of round robin.
MacHamRadio.com source: fldigi readme.txt, updated 2017-01-30