Softpedia >Windows >Internet >Other Internet Related >TQSL (Trusted QSL) >  Changelog

TQSL (Trusted QSL) Changelog

What's new in TQSL (Trusted QSL) 2.7.3

Apr 9, 2024
  • This release contains several minor updates which have accumulated since 2.7.

New in TQSL (Trusted QSL) 2.7.2 (Dec 17, 2023)

  • Trusted QSL software is compatible with all versions of the Windows operating systems that Microsoft currently supports.

New in TQSL (Trusted QSL) 2.7.1 (Nov 6, 2023)

  • This version of Trusted QSL (TQSL) has new features as well as corrections for defects found since TQSL 2.6 was released.

New in TQSL (Trusted QSL) 2.6.5 (Sep 13, 2023)

  • Change the widget used for pulldown menus because Microsoft's Windows 11 22H2 preview broke them and Microsoft refuses to fix the bug.
  • Correct the portable callsign fix - it didn't work properly and didn't cover all cases.

New in TQSL (Trusted QSL) 2.0.1 RC 2 (Dec 30, 2013)

  • Word wrap "overlapping certificate" message properly
  • Fix crash that occurred when an error was displayed due to the automatic backup being performed at exit
  • Display errors that happen while saving creating callsign certificate requests more prominently
  • When prompting for a password, don't treat an empty password response as a cancel. Try to use that and report a password error if appropriate
  • When reporting errors, don't include the filename of the proximate cause twice in the same error message
  • Don't notify users of pending callsign certificate requests with the "are you ready to install" prompt. This is confusing as it seems to indicate that TQSL has the .TQ6 already downloaded and ready to install. Since we can't tell when LoTW has delivered the e-mail, don't prompt for the TQ6 at every startup
  • Use the LoTW certificate status web query to determine if any callsign certificates are current. Store this information when updates are done default, once daily) and use that to inform users that the callsign certificate they are using are no longer valid
  • Move the update operations performed at startup to a separate thread so the GUI can initialize while this work is ongoing. This replaces the 2.0 behavior of starting the updates (and blocking the GUI) two seconds after the GUI appeared. This also corrects a potential deadlock on OSX where the first-time user message could appear along with an update dialog, both of which locked each other out
  • Correct callsign certificate password handling to use UTF-8 for any new passwords. On Windows, try UTF-8 then UCS-2 to unlock
  • Issue more helpful error messages when errors occur while parsing an ADIF file, including what field is causing the error
  • Correct problem where using characters like "" or quote in a station location field could cause restoring a .tbk file to fail with a syntaxerror
  • Properly handle non-ASCII characters in station location names and in callsign certificate request name/address fields. Store these in a form that allows transport between UNIX and Windows
  • When asking about how to handle duplicate QSOs, don't count duplicate QSOs and QSOs with bad callsigns as "new" - ignore them
  • When importing certificates, default to .tq6 files
  • Force the callsign certificates and station locations pane of the UI to be fixed size. This fixes long lists of certificates or locations to use a scrollbar rather than having the pane stretch the whole UI

New in TQSL (Trusted QSL) 2.0 (Nov 8, 2013)

  • Merge tqslcert into tqsl. Update the UI to be more user friendly.
  • For the Callsign Certificates tree display, don't display the
  • certificate provider list if there's only one provider.
  • Allow users to back up and restore their TQSL configuration in a portable
  • file. Automatically back up the configuration to a user-specified directory
  • (or to a default one) unless this is disabled.
  • Add diagnostic logging capability. This is used to store a verbose log
  • from cURL and to write a trace log that can be used by the developers to
  • help determine the source of defects.
  • Display unique icons in the certificate tree to allow expired and superseded
  • certificates can be distinguished.
  • Detect and report invalid frequencies in ADIF files (outside of ham bands,
  • entered in KHz versus MHz.)
  • Validate the format of Grid Squares when they're entered for a station
  • location. This also fixes the case to be normal, upper case for the Field,
  • lower case for the subsquare (FM18ju, for example).
  • Other changes:
  • Correct the defect that could cause invalid QSOs (bad call signs, for
  • example) to result in a cancellation message from an attempt to sign the
  • log but not provide detail on what QSO failed.
  • Automatically back up the user's configuration whenever TQSL closes.
  • Display the versions of the major software packages built into TQSL as part
  • of the "Help/About" text.
  • Don't ask the user to choose the file type for certificate load operations,
  • just provide a file open dialog and allow them to choose.
  • When issuing a callsign certificate request, default to "signed" unless there
  • are no usable certificates to be used to sign the request. Add text to the
  • dialog box explaining when unsigned requests should be used.
  • Remove the initial "Certificate Providers" page from the certificate
  • request wizard as it serves no current purpose.
  • Always display all callsign certificates, including expired and superseded
  • certficates.
  • Use consistent terminology throughout - "Callsign Certificate" and "Station
  • Location".
  • Replace atoi() calls with strtol() to correct parsing of strings like '012'
  • so they are not treated as octal.
  • Enforce frequency entry in the ADIF editor, ensuring that frequencies are
  • entered correctly (in MHz) and within an amateur band. Reject frequencies
  • that are not consistent with the BAND setting.
  • Correct the exit code for circumstances when -a abort is used and an bad QSO
  • is detected. Display the error information on that QSO before exiting.
  • Detect new verions of the TQSL configuration file when performing the
  • "check for updates" operation (manual or automatic) and allow the user to
  • update the configuration file if there is a newer one available.
  • Add new command line options "-b" to select the start date for QSOs to be
  • signed (begin) and "-e" to select the end date for QSOs to be signed.
  • Warn users on startup when they have a certificate that's going to expire
  • soon (in less than 60 days).
  • Back up certificate details (address, entity) when backing up as .p12 file.
  • Change title of certificate request window to reflect new or renewed
  • certificate.
  • Add the ability to automatically upload a certificate request.
  • Make the preferences window a top-level window so it doesn't block
  • activity in the help screen, etc.
  • Delete obsolete mode maps when signing a log.
  • When creating a station location, default to the callsign selected on
  • the locations tree if one is selected.
  • Add a button to the Log Operations window that opens the Logbook of the
  • world website.
  • Add a new command line option, -n, which checks for new versions of critical
  • TQSL files then exits. This is designed for use by logging programs that
  • operate TQSL on behalf of the user.
  • Add network proxy preference settings to allow users to use the TQSL network
  • based functions on networks that require all traffic to use a proxy.
  • Grab window focus when prompting for the certificate password to ensure that
  • the password window appears on top of the calling logger.
  • Simplify the messages displayed on certificate import (relegate the details
  • to the diagnostic log).
  • Detect additional cURL errors and translate them into more user-friendly
  • text.
  • Don't use "Private Key" in certificate load error messages - use certificate
  • request. Provide the callsign associated with certificate loading errors.
  • Display detailed error on certificate import errors.
  • Display system error reason when attempts to update the TrustedQSL
  • configuration file fail.
  • Track multiple pending certificate requests and warn the user when they try to
  • ask for a new or renewed certificate for callsigns where requests are already
  • pending.
  • Fix pathname separators so Windows always uses "\" for folder/directory names,
  • not mixed forward and backward slashes.
  • Add more information to signing progress display including processed, error,
  • and duplicate counts.
  • Recover from invalid ADIF files by ignoring invalid data until the next EOR
  • (end of record) field is seen.
  • Add working directory string to diagnostic log.
  • Update documentation to reference differences for Mac OS X menus.
  • Delete pending log file when signing cancelled.
  • Fix crash when location entity data is missing.
  • Display the DXCC entity name in location properties, not the entity number.
  • Correct Grid Square parsing to allow 'a' and 'z' in subsquare fields.
  • Update documentation to reference Mac OS X GUI fields and menu layout.
  • Move Diagnostic Mode menu to File menu - the OS X Help menu doesn't allow
  • checked items.
  • Correct other instances of DXCC entity number being used in user messages
  • to emit entity name, not the number.
  • Generate an error message on startup when stale mode maps are in place.
  • Don't allow a user to redefine a standard mode.
  • When the user chooses to not ignore errors in a log, don't save or
  • upload it.
  • Fix the way user dialog boxes (for things like date range, passwords, and
  • requests for how to handle errors) get instantiated so that the windows can
  • appear on top of logging programs using command line log signing.
  • Attempt to determine the field containing the call-worked data in unknown
  • Cabrillo contests without requiring the user to define a custom contest.
  • Update the "Ignore Errors" dialog to have "Ignore" and "Cancel" options
  • and to describe what each of those does.
  • Correct batch/quiet mode (-q or -x command line options) to avoid unexpected
  • windows from popping up before a dialog (password, errors, date range, etc.)
  • Always print out the TQSL version number at the beginning of output for
  • command line applications.
  • Use new application icons contributed by K1GQ.
  • Correct regression where duplicate QSOs would result in an action prompt
  • even though "-a abort" was specified on the command line.
  • Don't display the TQSL version number when "-n" is used on the command line.
  • Strip leading and trailing spaces from the location name passed on the
  • command line.
  • Properly handle and report upload errors displayed by the LoTW website.
  • Install TQSL icon when "make install" used on Linux.
  • Make the new icons optional.
  • Correct the suppression of the TQSL version number when "-n" is used
  • on the commmand line.
  • Report errors when critical files cannot be opened (station data,
  • certificates, etc.)
  • Correct the behavior when the user selects a callsign or a location in the
  • station location pane then clicks "Create new station location". The callsign
  • selected was used in the location setup, but the DXCC entity was not properly
  • selected.
  • Only display the DXCC entity once in the station location page. This fixes
  • the display when there are multiple callsign certificates for a given callsign
  • (one valid and one expired, for example). This defect would cause TQSL to show
  • a pulldown menu with multiple copies of the same entity name.
  • Suppress warning messages when the user has no locations defined or callsign
  • certificates installed as this is normal for an initial setup.
  • When "Sign and Save" or "Sign and Upload" are used, first check if the user
  • has any callsign certificates installed. The former behavior would ask for
  • the input and output files, then try to select a station location. Since
  • there are none, offering to create a station location would then fail.
  • Trim extra spaces from station location fields. These could cause
  • signing to fail as LoTW was removing these but TQSL was not.
  • Update TQSL to provide the current LoTW configuration file (v2.5)
  • Correct error messages on version update website failures, so that it's
  • clear that it was the check that failed, not the download. Increase the
  • version check timeout slightly to limit premature check failures.
  • When performing the automatic update check at startup, wait for the main GUI
  • window to appear. Provide a status message in the window until the update
  • check completes. This keeps TQSL from appearing to hang at startup if the
  • update check is slow.
  • Correct command line behavior to not pop up a window when invoked then
  • close that window. Fix duplicate handling error introduced at RC6.

New in TQSL (Trusted QSL) 1.14.3 (Jul 6, 2013)

  • On Windows, use a newer verions of libcurl that doesn't suffer from the defect fixed by http://support.microsoft.com/kb/975858.
  • On all platforms: show some additional libraries' versions in the about screen

New in TQSL (Trusted QSL) 1.14.2 (Jun 8, 2013)

  • Fixed an error when the TrustedQSL directory had Unicode characters, don't prompt for updates when called silently, fail properly when the user chooses to not ignore signing errors

New in TQSL (Trusted QSL) 1.14 (May 7, 2013)

  • Major feature additions:
  • Upload log files directly from TrustedQSL! Simply choose "sign and upload"
  • from the File menu and your log will signed and uploaded automatically with
  • no extra work.
  • Command line flag '-u' has been added to expose this functionality to
  • tools authors.
  • The return value from tqsl can be used to determine whether the signing
  • or upload succeeded or failed, and why
  • 0=success; log signed and uploaded and accepted without incident
  • 1=Cancelled by user
  • 2=The log was rejected by the LoTW server
  • 3=The response from the LoTW server was unexpected or unrecognized
  • 4=An error occurred in tqsl
  • 5=An error occurred in tqsllib (probably a bad filename)
  • 6=Unable to open input file
  • 7=Unable to open output file
  • 8=All QSOs were duplicate or out of date range (no QSOs written)
  • 9=Some QSOs were duplicate or out of date range (some QSOs written)
  • 10=Command syntax error
  • 11=LoTW network connection failed (no network or LoTW is unreachable)
  • The exit status is also written to Standard Error (stderr) in an easily
  • recognized format.
  • Automatically check for updates. If a new version is available, you will be
  • periodically prompted to download and install it. You can also check manually
  • Duplicate checking. Any QSOs that have been successfully uploaded to Logbook
  • of the World or saved to a file are registered in a database. Any exact
  • duplicates are automatically stripped from future logs. This can be disabled
  • on a case-by-case basis, in case a log was signed but never uploaded, or
  • there was a server issue that led to an upload going unprocessed.
  • TQSL will now ensure that the CQ and ITU zones, and subdivisions if any
  • US state/county, Canadian province, Russian oblast) are valid with respect
  • to each other. This should reduce the incidence of swapped CQ/ITU zones and
  • in general should help ensure that more accurate location data is uploaded.
  • When an attempt is made to use a location with errors (such as CQ/ITU
  • zones being reversed) the user is notified to correct the errors.
  • Installer on Windows is now a Microsoft Windows Installer package, instead of
  • an executable. This will allow for easier and cleaner upgrades
  • Added a new command line option, '-a', to allow command line users to
  • control user interaction. This option takes a value from the set ask,
  • abort, compliant, or all. For '-a ask', TQSL will ask users how to handle
  • duplicates and date mismatches. '-a abort' will cause signing to terminate
  • immediately when an error occurs. '-a compliant' will cause only correct
  • new or in date range) records to be output, and '-a all' will cause all
  • of the input records (including duplicates) to be signed. Prompts for errors
  • date ranges bad, bad callsigns) will be suppressed for '-a compliant'
  • or '-a all', but cause immediate aborts when '-a abort' is used. '-a ask'
  • prompts the user in those cases.
  • Minor changes:
  • TQSL/TQSLCERT now have window icons
  • Double-clicking an entry in the "Choose station location" window for signing
  • now selects it, instead of opening it for editing
  • Command line parsing has been rewritten and should be more robust. Also,
  • command-line documentation is available with '-h'
  • Files to sign and save are now prompted before location and date range
  • The build number is now shown in the About box; please include this when
  • asking for help
  • The final confirmation before signing includes the signing station location
  • Output files on Unix systems are provided with a default .tq8 extension
  • The "Edit station location" window title now contains the callsign and
  • station location name
  • Station locations can no longer be defined using expired or superceded
  • certificates
  • Users are no longer prompted for a password while importing a .p12 file
  • unless the file has a password set
  • When importing a certificate, detailed information is provided on the
  • progress of the operation as well as the reason for any errors
  • Dozens of bug fixes and potential or real crashes fixed.
  • TQSL/TQSLCERT and the rest of TrustedQSL now built with the CMake build system
  • TQSL/TQSLCERT are now built with MSVC on Windows.

New in TQSL (Trusted QSL) 1.14 RC4 (Mar 27, 2013)

  • Major feature additions:
  • Upload log files directly from TrustedQSL! Simply choose "sign and upload" from the File menu and your log will signed and uploaded automatically with no extra work.
  • Command line flag '-u' has been added to expose this functionality to tools authors. The return value to determine whether the upload succeeded or failed, and why
  • 0=success; log signed and uploaded and accepted without incident
  • 1=soft fail (empty or all dupe log?)
  • 2=active reject (the server received the log and decided to reject it)
  • 3=passive reject (the server is probably down; unexpected response)
  • 4=hard fail (internal error)
  • 5=tqsllib internal error (probably a bad filename)
  • Automatically check for updates. If a new version is available, you will be periodically prompted to download and install it. You can also check manually
  • Duplicate checking. Any QSOs that have been successfully uploaded to Logbook of the World or saved to a file are registered in a database. Any exact duplicates are automatically stripped from future logs. This can be disabled on a case-by-case basis, in case a log was signed but never uploaded, or there was a server issue that led to an upload going unprocessed.
  • TQSL will now ensure that the CQ and ITU zones, and subdivisions if any (US state/county, Canadian province, Russian oblast) are valid with respect to each other. This should reduce the incidence of swapped CQ/ITU zones and in general should help ensure that more accurate location data is uploaded.
  • When an attempt is made to use a location with errors (such as CQ/ITU zones being reversed) the user is notified to correct the errors.
  • Installer on Windows is now a Microsoft Windows Installer package, instead of an executable. This will allow for easier and cleaner upgrades
  • Added a new command line option, '-a', to allow command line users to
  • control user interaction. This option takes a value from the set ask, abort, compliant, or all. For '-a ask', TQSL will ask users how to handle duplicates and date mismatches. '-a abort' will cause signing to terminate immediately when an error occurs. '-a compliant' will cause only correct new or in date range) records to be output, and '-a all' will cause all of the input records (including duplicates) to be signed. Prompts for errors date ranges bad, bad callsigns) will be suppressed for '-a compliant' or '-a all', but cause immediate aborts when '-a abort' is used. '-a ask' prompts the user in those cases.
  • Minor changes:
  • TQSL/TQSLCERT now have window icons
  • Double-clicking an entry in the "Choose station location" window for signing now selects it, instead of opening it for editing
  • Command line parsing has been rewritten and should be more robust. Also, command-line documentation is available with '-h'
  • Files to sign and save are now prompted before location and date range
  • The build number is now shown in the About box; please include this when asking for help
  • The final confirmation before signing includes the signing station location
  • Dozens of bug fixes and potential or real crashes fixed.
  • TQSL/TQSLCERT and the rest of TrustedQSL now built with the CMake build system
  • TQSL/TQSLCERT are now built with MSVC on Windows.
  • Windows 98 support has been dropped. This will be one of the last releases to support Windows 2000.
  • This will be one of the last releases to support OS X on PowerPC systems.

New in TQSL (Trusted QSL) 1.13 (Mar 27, 2013)

  • No functional changes. Update to sync to updated tqsllib; updated build tools.

New in TQSL (Trusted QSL) 1.12 (Mar 27, 2013)

  • When asking for the password to unlock a private key, say what callsign it's for.
  • Remember certificate requests and assist the user with importing the .tq6.
  • Prompt user to save their certificate after importing a .tq6 signed certificate.
  • Suppress display of superseded certificates, controlled by a tqslcert preference setting.
  • Fix windows wxWidgets crashes with several wizards (cert renew, new cert,
  • etc.)
  • Add checkbox to allow bypassing state selection.
  • Fix crash on Windows when new certificate request wizard is started.
  • Added support for validating zone numbers and requiring them.
  • Allowed batch mode (-x) without displaying windows
  • When double-clicking an entry on the "Edit Station Locations" dialog, open that entry for edit, don't just close the modal dialog.
  • Change the "OK" button on the "Edit Station Locations" dialog to "Close" as that's what it does.
  • Update password dialogs to enable "enter" to activate when possible.
  • Add "-p " and "-o " arguments to tqsl.

New in TQSL (Trusted QSL) 1.11 (Mar 27, 2013)

  • Added command-line option -d. (See on-line help for details.)
  • Modified string handling to be compatible with Unicode versions of wWindows/wx Widgets.
  • Certificate request wizard now checks for date overlap of request with existing certificates. This allows non-overlapping requests to be generated. (TQSLCERT)
  • Help-contents file tags now contain "type" parameter so that packages built with wxWindows >= 2.4 will show the help contents properly.

New in TQSL (Trusted QSL) 1.10 (Mar 27, 2013)

  • Added command-line parameters and help page for same. (TQSL)
  • Windows build now links the expat library statically, eliminating the need for libexpat.dll. (TQSL/TQSLCERT)

New in TQSL (Trusted QSL) 1.09 (Mar 27, 2013)

  • ADIF editor now handles seconds in the TIME_ON field. (TQSL)
  • User now gets chance to re-enter failed password during signing.(TQSL)
  • Expanded explanation of QSO date-range dialog during signing. (TQSL)
  • After loading new configuration data, DXCC list in CRQ wizard was hosed.
  • (TQSLCERT)