From f95d8363ef01dd4c67d54881001c83ca9fe8bf9b Mon Sep 17 00:00:00 2001 From: Arnis Armans Date: Wed, 9 Sep 2026 18:44:44 +0300 Subject: [PATCH] Default to Yes when exporting a callsign KLog considers invalid showInvalidCallMessage() asks whether to export a callsign the validator rejected, with No as the default button. Since the dialog itself says the call may well be valid and wrongly flagged, defaulting to No means an accidental Enter or Escape silently drops a real QSO from the export. The QSO stays in the log and is marked as sent, so nothing looks wrong, but it never reaches LoTW or Club Log. I found this when my log showed one QSO more than the exported ADIF. Example: 4JT3DJ (Azerbaijan), 35,245 lookups on QRZ, QSL via Club Log OQRS and the bureau: https://www.qrz.com/db/4JT3DJ Defaulting to Yes keeps the warning but makes the safe answer the default one. --- src/dataproxy_sqlite.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/dataproxy_sqlite.cpp b/src/dataproxy_sqlite.cpp index 45322f93..34443fee 100644 --- a/src/dataproxy_sqlite.cpp +++ b/src/dataproxy_sqlite.cpp @@ -8828,7 +8828,7 @@ bool DataProxy_SQLite::showInvalidCallMessage(const QString &_call){ msgBox.setText(aux); msgBox.setInformativeText(tr("Exporting wrong calls may create problems in the applications you are potentially importing this logfile to. It may, however, be a good callsign that is wrongly identified by KLog as not valid.")); msgBox.setStandardButtons(QMessageBox::Yes | QMessageBox::No); - msgBox.setDefaultButton(QMessageBox::No); + msgBox.setDefaultButton(QMessageBox::Yes); int ret = msgBox.exec(); switch (ret) { case QMessageBox::Yes: