TQSL 2.5 Release candidate (2.5-rc1) available for testing
I'm getting ready to release the next version of TQSL, pending
translation updates which I'm going to be sending out shortly.
Here's the list of major changes in TQSL 2.5:
- If a QSO provides a Band and a Frequency, and that frequency is out
of range for the given band, then the frequency is ignored.
- Callsign Certificate requests for US hams use the ULS database for
verifying the callsign and for providing address information. This
also includes validation for 1x1 callsigns.
- When creating a callsign certificate, the first question is now for
what kind of call. Personal, former, club, etc. This makes the rest of
the process easier as defaults can be applied.
- When displaying the list of DXCC entities for a callsign
certificate, the deleted entities are now pushed to the end of the
list. The word "DELETED" in their names can now be localized so it's
easier for non-english speakers to understand.
- When loading a callsign certificate, TQSL no longer asks for a
password for that certificate. This can be re-enabled by a preference
- The TQSL ADIF editor now emits proper MODE/SUBMODE for modes that
- TQSL checks for operating as an elevated ("As Administrator")
account on Windows and complains. A user is allowed to permanently
bypass that check.
- References to "Duplicate" QSOs were changed to "previously uploaded".
- When editing a Station Location, do not override the existing data
with ARRL or ULS address data. Those are now only used when station
locations are initially created.
Lots of changes, especially around the callsign certificate processes,
so testing here would be much appreciated.
OSX 32-bit: https://www.rickmurphy.net/lotw/tqsl-legacy-2.5.dmg
Rick Murphy, CISSP-ISSAP, K1MU/4, Annandale VA USA