What's new in Trusted QSL 2.1 Beta
Oct 23, 2014
- When signing a log from the command line in "batch" mode (with -x specified), don't stall waiting on other copies of TQSL to complete signing before processing the command-line log. Instead, report an error message stating that the database is busy. This corrects an issue where logging programs calling TQSL to sign a log could
- appear to be "hung".
- Update TQSL to be more tolerant of non-english characters in file and directory names.
- Allow station locations to have callsign unspecified ('[None]').
- These locations can be used for signing a log by selecting the correct callsign certificate from a list, with the callsign certificate that expires the latest chosen by default.
- Further changes for accessibility improvements, including not using changing text fields on dialog boxes to indicate errors.
- Update TQSL to interact better with accessibility libraries. These changes have been tested with MacOS VoiceOver.
- Properly handle station locations with callsign set to "NONE". They can't be used to sign a log, but they can be created and edited while waiting for a valid callsign certificate.
- Allow TQSL's messages to be translated to the local language.
- When update checks are being performed and the Logbook website is not reachable, don't keep trying after the initial failure.
- Improve startup performance and performance with a large number of callsign certificates.
- Add the ability to localize TQSL by allowing translation of many of the messages generated by TQSL.
New in Trusted QSL 2.0.2 (Apr 17, 2014)
- Use OpenSSL 1.0.1g to correct the Heartbleed bug.
- Add a newline after "Signing using.." message when signing a log so any errors show up under that message, not tacked onto the end of it.
New in Trusted QSL 2.0.1 (Apr 15, 2014)
- Defects Corrected:
- TQSL allowed multiple log signing operations to be performed at once (for example, starting to sign a log, which then stalls waiting for the user to respond to a dialog box. While waiting for the first log, another log is submitted for signing). This could cause the QSO database to become corrupted.
- TQSL 2.0.1 does not allow multiple log signing operations.
- When a callsign certificate is about to expire, TQSL would issue a warning and offer to renew the callsign certificate even though the user had already submitted a renewal. This has been corrected to not ask the user after they have created a renewal request.
- When editing a station location where there the associated callsign certificate is no longer installed, TQSL would fall back and use the user?s first callsign certificate. This has been corrected to warn the user that the location cannot be used.
- The checks for updates performed during start-up of TQSL could cause TQSL to hang or crash on some Linux systems. This has been corrected so that the updates are handled properly on all platforms.
- Certain command line parameters (for example, "-p"), would cause TQSL to hang if no value was provided. This has been corrected to properly handle the missing parameter.
- Station Locations with non-English characters would cause TQSL to be unable to process the station locations. Also, location names with leading or trailing spaces could not be used. TQSL has been updated to properly handle the full range of characters.
- When prompting a user for the Callsign Certificate password, TQSL would treat an empty response as if the user cancelled the request. TQSL now treats this as an empty password.
- TQSL would notify a user of a pending Callsign Certificate request each time it was started, even though the pending request had not been processed by LoTW. Users interpreted this as an indication that the request was completed, causing them to re-submit. TQSL no longer issues this notification.
- When signing a log, TQSL would count duplicate QSOs and QSOs with bad callsigns as "new" QSOs. These are no longer counted as new QSOs.
- The TQSL user interface did not properly adjust for users with a large number of Station Locations and/or Callsign Certificates. The layout is now fixed and allows for scroll bars to allow viewing the list of entries properly.
- Major feature Additions:
- Update the messages displayed during callsign certificate creation to make it clear when signed requests are appropriate.
- Warn when a duplicate certificate request is being created that there are pending operations and that the user should wait for the outstanding request to be processed.
- When a user tries to sign a log using a Station Location that refers to an invalid Callsign Certificate, refuse the signing operation and let the user know that the Callsign Certificate is invalid.
- For uploaded files, use .tq8 as the extension, not the original .adi/.log to avoid user confusion.
- TQSL now uses an online service managed at the LoTW web site to manage the status of callsign certificates. This allows TQSL to determine when a callsign certificate has been replaced by a newer one and issue appropriate messages when a user tries to use an out-of-date callsign certificate.
- When TQSL detects an error while processing an ADIF file, more detail is provided about the cause, including what part of the ADIF file is not recognized.
New in Trusted QSL 2.0.1 RC (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 (by 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.
- 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 syntax error.
- 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 Trusted QSL 1.14.2 (Jul 1, 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 ignoresigning errors.
New in Trusted QSL 1.14.1 (Jul 1, 2013)
- Minor bug fixes to internet functions and the command line parser, hang fixed on OSX, removed unnecessary field from upload.