Update the icon for a “Waiting for Callsign Certificate” from a slashed circle to a clock. This avoids the problem where a user gets all the way through configuring a new station location but then can’t save it.įix an error on OSX systems where the “Edit Station Location” icon was getting squashed. Verify that the user has the ability to write files to the TQSL working directory when TQSL starts up. Replace the term “duplicate” when referring to QSOs which have already been uploaded to LoTW – calling them “previously uploaded” is less confusing as it says what’s wrong with those QSOs. This corrects the confusion between, for example, “GERMANY (DELETED)” and “FEDERAL REPUBLIC OF GERMANY”. The word “DELETED” in the entity name is now localizable. When listing DXCC entities, the list now has the deleted entities moved to the end. When submitting requests for US 1×1 callsigns, which must always be a signed request, ensure that the flow properly marks the callsign as 1×1, and that the requester has a valid callsign certificate that can be used to sign that request. There is a preference setting to re-enable this if desired. TQSL no longer asks for passwords for callsign certificates when they are created. The user is allowed to temporarily or permanently ignore that warning. Use an ARRL-supplied web service with ULS data to pre-fill station location information.ĭetect when the user runs TQSL “As Administrator” on Windows systems and warn that this is not recommended. Setting those when creating a new station location is appropriate, but editing an existing location should not cause default values to be applied.Ĭorrect ADIF output from the embedded ADIF editor so the proper mode/submode formation is generated.Ĭorrect a defect that was causing automatic updates on Windows to fail when the user’s directory contained non-ASCII characters.Ĭorrect a defect that could cause TQSL to crash when backing up to a. Previously, TQSL would fill in fields like county or state. When editing an existing station location, TQSL no longer forces default values for information fields. (This was a rare situation that would happen when a root was within 24 hours of expiring.) TQSL no longer displays a spurious error message about expired root certificates when installing a. The following list describes the major changes in the v2.5 release of Trusted QSL. Thanks to the following for their assistance:Ĭhinese: Caros, BH4TXN Finnish: Juhani, OH8MXL Hindi: Manmohan, VU3YBH German: Andreas, DF4WC Italian: Salvatore, IV4FYV Japanese: Akihiro, J元OXR Portuguese: Nuno, CT2IRY Russian: Vic, US5WE Turkish: Ojuzhan, TA2NC Spanish: Jordi, EA3GCV This could not have been done without the help of the volunteers who have contributed translations for TQSL. TQSL 2.5 has been “localized” to allow use in the native language of non-English speakers. #Macloggerdx tqsl location install#For Linux systems, unpack the tar file and read the INSTALL file for directions. #Macloggerdx tqsl location 32 bit#(Note that the “tqsl-legacy” disk image is for legacy Mac systems – 32 bit Intel and PowerPC.) Direct the installer to “Replace All”, which will uninstall old files. #Macloggerdx tqsl location mac os#On Mac OS X, open the disk image (.dmg) file and drag the “Trusted QSL” folder to your Applications folder. On Windows, simply run the TQSL 2.5 installer, which will automatically uninstall older versions of TQSL (and, if installed, TQSLCert). On all three supported platforms (Windows, MacOS, and Linux), installing TQSL 2.5 will replace older versions of Trusted QSL while preserving your Callsign Certificates, Station Locations, and preferences. TQSL 2.5 can be installed to upgrade any older version of TQSL. #Macloggerdx tqsl location update#This release also includes an update to the most recent TQSL configuration file. This version of Trusted QSL (TQSL) has new features as well as corrections for defects found since TQSL 2.4.7 was released.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |