Upgrade tqsl from 2.0.2RC4 to 2.0.3
----------------------------
tqsl-2.0.2 to 2.0.3 change:
----------------------------
(tqslilb: 2.4)
Fix defect that doesn't allow adding station locations if only a single
callsign certificate is installed.

(following diff is manually editted, tabs are deleted)
diff -urp tqsl-2.0.2/src/location.cpp tqsl-2.0.3/src/location.cpp
--- tqsl-2.0.2/src/location.cpp 2014-07-13 05:18:13.000000000 +0900
+++ tqsl-2.0.3/src/location.cpp 2014-07-17 10:22:16.000000000 +0900
@@ -1152,6 +1152,9 @@ update_page(int page, TQSL_LOCATION *loc
                        field.idx = static_cast<int>(field.items.size());
                field.items.push_back(item);
        }
+      if (field.idx == -1 && field.items.size() == 1) {
+              field.idx = 0;
+      }
        if (field.idx >= 0) {
                field.cdata = field.items[field.idx].text;
        }
----------------------------
tqsl-2.0.2RC5 to 2.0.2 change: (Authors note):
----------------------------
As I've had no comments on the 2.0.2-rc5 beta, I've decided that it's time to release it.

The kits on sourceforge have been updated to the final v2.0.2 release.

https://sourceforge.net/projects/trustedqsl/files/TrustedQSL/v2.0.2/

The README there is the preliminary release notes.
Thanks to everyone for the help with testing and reporting issues.
----------------------------
tqsl-2.0.2RC4 to 2.0.2RC5 change:
----------------------------
This release fixes a pair of related defects that have been there
since TQSL 1.x

When you create a station location, you associate it with a callsign
certificate. When you sign a log, you select a location for signing,
which then uses the callsign to select the right callsign certificate.

The problems happen when you do unexpected things with those
certificates.

If you create a station location for K1MU, then delete all of the
certificates for K1MU, then signing a log would cause an "Invalid
Argument" error. TQSL has been corrected to now display an error that
there are no valid callsign certificates.

Similarly, if you create a station location and then let the
associated callsign certificate to expire, trying to sign using that
location would also give an unhelpful "Invalid Argument" message.

When there were no matching certificates, displaying the properties of
a station location would display an incorrect callsign.

These defects have been corrected in RC5 so that useful error messages
are displayed for these cases.

(mef)