Changelog

Version 1.2.1

31 August 2026

The first release since 1.1.9. Three areas changed: contacts can now be uploaded to a QRZ.com logbook, each contact records the station it was made from rather than looking that up at export time, and operator records have a screen of their own.

Upload to your QRZ.com logbook

Contacts can be sent to a QRZ logbook as they are logged. Turn it on under My Station and paste the API key for the logbook you want them in.

• The queue is kept in the logbook file, not in memory, so a contact logged somewhere with no signal goes up on the next run that reaches QRZ. Closing the program does not lose it.
• Only contacts logged after the setting is switched on are candidates. Turning it on does not publish your back log, and importing an ADIF file never sends someone else's contacts to your account.
• Editing a contact QRZ already holds re-sends it as a replacement, so it is corrected rather than duplicated.
• A contact QRZ refuses is marked failed and left alone until you edit it. A contact that could not be sent because the network was down stays queued.

Uploading requires a QRZ subscription at XML level or higher — QRZ's requirement, not this program's. The API key is stored on this machine only and is deliberately left out of an exported station profile, since that file is meant to be carried between devices.

Contacts remember the station they were made from

Previously only the callsign was recorded on each contact; everything else about your station was read at the moment of export. Move house, or type a new radio over an old setup, and every QSO you had ever made would quietly export the new details.

Each contact now stores its own grid square, city, state, postal code, CQ and ITU zones, coordinates, rig and antenna. Change any of it and past contacts still export what they were actually made with.

Contacts logged before this release keep the fallback behaviour: location is not back-filled, because there is no record of where the station used to be and copying today's answer would invent history. Rig and antenna are back-filled from the setup each contact named, since that setup is still on file and its rig is what those contacts have been exporting all along.

An Operators tab

An operator record describes a person, not one contact. It now has its own tab rather than living on the QSO form.

• A roster of everyone worked, with their contact count and when you last worked them. Search matches on callsign.
• The detail view edits the record and has a Look up on QRZ button that refreshes it from the callbook.
• Remove is offered only for an operator with no contacts on file. Removing one with contacts would take those contacts with it.
• The Operator card on the QSO screen is now read-only, with a link through to this tab. One place writes the record, so a stale copy on the QSO form can no longer overwrite an edit made here.

Callsign modifiers no longer split one person into several records. K3TCM, K3TCM/P and KH6/K3TCM are one operator with one set of notes. Exports are unaffected: each contact records the callsign actually worked, so a portable contact still exports as K3TCM/P.

If your logbook already contains an operator filed under more than one form of the same callsign, those rows are left as they are. Merging them means choosing whose name, QTH and notes survive, which is a decision about your log rather than one to make silently — the roster is the place to see and fix them.

Also in this release

• Operator notes typed on the QSO form are saved. They were never written to the logbook at all.
• The Logbook tab has a callsign filter you can type into. Clicking a callsign in a row still fills it in, and it matches on part of a callsign as you type.
• The Windows installer offers a desktop shortcut and asks before creating either shortcut, rather than deciding for you.
• The Android build no longer reports itself as 1.1.0.

Upgrading

Install over the top of the existing version. Your logbook file is untouched by the installer and is upgraded in place the first time 1.2.1 opens it; nothing already in it is changed or discarded.

Going back to 1.1.9 afterwards is possible but not advised: the older version will open the upgraded file and simply ignore the new fields, so anything logged or edited there records no station snapshot and never queues for upload. Copy the file first if you intend to try it.