| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
-----------------------------------------------------------------
Following is not for explicit 2.2.1 release but for 2.2,
(attached to mail from Rick Murphy on 2015/12/31 as
Subject: TrustedQSL 2.2 final release is available for download)
-----------------------------------------------------------------
Trusted QSL V2.2 Release Notes
This version of Trusted QSL (TQSL) has corrections for defects found since
TQSL 2.1 was released (including the updates made for TQSL 2.1.1, 2.1.2,
and 2.1.3) as well as improvements to permit TQSL and Logbook of the World
to support the National Parks on the Air competition.
TQSL 2.2 can be installed to upgrade any older version of TQSL. Downgrade
to TQSL 2.1.3 can be seamlessly performed by uninstalling TQSL 2.2 and
reinstalling TQSL 2.1.3.
On all three supported platforms (Windows, MacOS, and Linux), installing
TQSL 2.2 will replace older versions of Trusted QSL while preserving your
Callsign Certificates, Station Locations, and preferences. On Windows,
simply run the TQSL 2.2 installer, which will automatically uninstall
older versions of TQSL (and, if installed, TQSLCert). On Mac OS X, open
the disk image (.dmg) file and drag the "Trusted QSL" folder to your
Applications folder. Direct the installer to "Replace All", which will
uninstall old files. For Linux systems, unpack the tar file and read the
INSTALL file for directions.
The following list describes the major changes in the v2.2
release of Trusted QSL.
TQSL changes
Defects Corrected:
Fix a defect that could cause saving of Calllsign Certificate private keys
to be suppressed.
When renewing a Callsign Certificate, entering an invalid password would
display an incorrect "Invalid Argument" error versus displaying the proper
"Invalid password" error. Under some circumstances, this could cause the
related Callsign Certificate to be lost.
Accept C7 and 4Y as valid callsign prefixes.
When installing a Callsign Certificate fails, display the callsign and
serial number to facilitate troubleshooting.
When deleting Callsign Certificates and Station Locations, save a copy to
allow those to be restored.
Reject QSOs that do not specify at least mode, band, date, and time.
Correct the TQSL ADIF editor to not use the local decimal point separator
for frequencies, as ADIF requires a period(.).
Major feature Additions:
Use Portuguese (Portugal) translations contributed by Nuno, CT2IRY.
Allow multiple dependent fields on a station location screen. This allows
both a county and a park entry to be modified when the US state changes
for a US Station Location.
|
|
|
|
- (patch-openssl__cert.cpp)
Add patch to define MAX_PATH macro
- Unable to package with x11/wxGTK30 yet
(upstream)
- Udate 2.0.3 to 2.1.2
-----------
TQSL-2.1.2
The following links are pointers to TrustedQSL (TQSL) V2.1.2, which is
a bug fix for the official TQSL 2.1 release.
Release Notes TrustedQSL-2-1-release.pdf
http://www.rickmurphy.net/lotw/TrustedQSL-2-1-release.pdf
|
|
- DEPENDS+= mozilla-rootcerts are removed, cert included now.
- Deleted SUBST_CLASSES+= macro_S to avoid name (_S) conflicts on NetBSD-5.*
(The probelm no longer exists)
- Correct MESSAGE (but this is to be committed separately)
(Upstream): Bump version 2.0 to 2.0.2RC4
---------------
This commit log compiled from that of wip/trustedQSL/Makefile by mef@
Sorry if typo or too compact.
2.0.2RC4 2014/06/07
- No pop up when prompting user for password when batch mode
- If QSO database is corrupted and can not be repaired, delete it
2.0.2RC3 2014/05/09
- Ensure station locations added (sign a log -> list of stn loc.)
- Restore from .tbk to restore multiple pending callsign
certificates for a given callsign
- Correct message when callsign cert. is uploaded
- Delete any older version, when renewed callsign is installed
- Correct the behaviour for non ascii directory name on Windows
- Correct the number of QSO in some case when signing
(ignoring might have shown negative number)
2.0.2RC2 2014/04/22
- Windows only
2.0.2RC1 2014/04/16
- OpenSSL update (Heartbleed). no practical attack anyway
(Windows only)
2.0.1RC9 2014/03/01
- Avoid application crash when database conversion for Open/Close
- Faster conversion of database
2.0.1RC8 2014/02/27
- Limit the number of copies of application running
(multiple run might have database corrution)
2.0.1RC7 2014/02/13
- When a callsign cert is about to expire (within 60 days), TQSL
warns. But even after user submitted renewal, it continued
- Correct the automatic backup directory (by from preference pane)
- Search Log files with .ADI, .ADIF also
2.0.1RC6 2014/02/05
- Copyright notice / date (only)
2.0.1RC5 2014/01/29
- Avoid crash at starting if certifiacate status file is empty
- Corrected for checking for new release even with -RC change
2.0.1RC4 2014/01/22
- Canadian province PQ/QC issue
- Correct start-up threads management
- (OpenSuSE Linux) for pending callsign requests
- Accept valid callsign only based on location
- Correct hang if command line argument is wrong
- Update message during callsign certificate creation
2.0.1RC3, 2014/01/13 (but hangs when reading cert_status.xml)
Two additional changes in TQSL 2.0 RC3:
-------------
A. Because new modes may not yet be specified in ADIF, and because
LoTW may not accept all modes specified in ADIF, TQSL enables you to
"map" a new mode to a mode or mode group recognized by LoTW; this
most often takes the form of mapping a new digital mode to the DATA
mode group. Versions of TQSL prior to 2.0 would allow you to map
modes accepted by LoTW. This version of TQSL will refuse to map a
mode that is accepted by LoTW. Any existing mappings of modes
accepted by LoTW will be automatically removed on startup; you will
be notified if this happens.
B. When submitting log files in Cabrillo format, previous versions of
TQSL submitted FM and PH modes as PHONE. TQSL 2.0 RC2 submits FM mode
as FM, and PH mode as SSB.
----------------------------
2.0.1RC2 2013/09/01
Contest name recognition is corrected (Re: JIDX)
|
|
Proposed at tech-pkg@ and supported by gdt@, thanks.
----------------------
Date: Saturday, September 21, 2013 8:32 PM
Subject: TQSL-2.0-RC6 Public release available
There's a new TQSL beta test release available for download.
This release corrects the following defects discovered since TQSL
2.0-RC5 (as well as severl enhancements).
Strip leading spaces and trailing spaces from station locations passed
on the command line to help correct for common user errors.
Display LoTW errors returned when a callsign certificate request fails
for some reason.
Record multiple outstanding certificate requests and delete the
pending status if the user deletes the corresponding callsign
certificate.
Remove an errant "M" on the certificate request signing page. Properly
wrap the text on that page for MacOS.
The TQSL version number is always displayed for command line usage
unless "-n" (check for new TQSL, configuration and program updates) is
used.
Added a new icon for TQSL contributed by K1GQ. The default shortcut
icon has not changed, but the new icon is available for selection.
Display an error when the TQSL configuration files (station locations,
callsign certificates, etc.) can't be opened. All earlier versions of
TQSL ignored these errors and started up with no callsign certificates
or station locations defined.
When a user selects a callsign in the Station Location window then
clicked on "Create new Station Location", the DXCC entity in the
station location wizard used the entity of the first callsign, not the
selected callsign.
The station location editor no longer shows multiple entries with the
same DXCC entity in the entity selection pulldown list when there are
multiple callsign certificates for a given callsign.
|
|
TrustedQSL is a LoTW (Logbook of The World) application to upload
QSO's (contacts) information onto Logbook servers maintained by the
ARRL (American Radio Relay League).
Logbook of The World - LoTW - is an exciting way for Radio Amateurs
to confirm two-way contacts they have made and use the confirmations
as credit toward various awards.
Because Logbook of The World uses double blind comparison, users
cannot see what other users have uploaded unless there is a matched
QSO.
|
