¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

UTC Clock

 

Hello, new to this program and I really like it. My question is that the the clock is showing a time that does not reflect the correct time and not UTC. How can I change this in the program??


Thanks
Richard - VE6PCO?


Release 0.28

 

Let me inform you that a new QLog release v0.28 is finished.

Changelog:
- [NEW] - Added ON4KST Chat Support
- [NEW] - Added Azimuth BeamWidth and Azimuth Offset to Antenna Profile
- [NEW] - Double-Clicking the IBP callsign in the online map tunes the frequency
- Fixed Browse button should open an expecting folder (issue #241)
- Fixed Reword QSL buttons and Settings in QSO Details and Settings (issue #242)

Changelog:
Wiki:


Release 0.27

 

Let me inform you that a new QLog release v0.27 is finished.

Changelog:
- [NEW] - Added HRDLog Support
- Fixed Text field alignment (issue #233)
- Fixed Rig/Rot Connection port type selection (issue #235)
- Fixed Incorrect Distance Value in WSJTX Widget (issue #236)
- Fixed Incorrect WSJTX locator target on the map (issue #237)

Changelog:
Wiki:


Release 0.26

 

Let me inform you that a new QLog release v0.26 is finished.

Changelog:
- [NEW] - Added user-defined layout for New QSO widget
- [NEW] - Pressing Spacebar in Callsign field skips RST fields
- [NEW] - Added user-defined URL for web lookup (issue #230)
- Fixed WSJTX QSOs should have an Operator Name from Callbook (issue #223)
- Fixed US call area suffixes not handled correctly (issue #226 thanks Florian)
- Fixed QSO Filter Detail allows to save an empty Filter Name (issue #228)

Changelog:
Wiki:


Release 0.25.1

 

Let me inform you that a new QLog release v0.25.1 is finished.

Changelog:
- Fixed Unexpected mode change when Setting Dialog is saved (issue #222)
- Fixed QSL_SENT field has an incorrect ADIF name (issue #225)

Changelog:


Re: Release 0.25

 

Hallo Ladislav,
ich habe deine (bleiben wir beim unter OM's vertrauten Du) Ausf¨¹hrungen einwandfrei verstanden, danke daf¨¹r.
Ich w¨¹rde f¨¹r meinen Teil auch eine Idee hinzuf¨¹gen, kann man das nicht in die Einstellungen machen, dass der Benutzer ausw?hlen kann, ob er die Daten aus QRZ.com ¨¹bernehmen will, oder nicht. Meiner Meinung nach, w?re dann allen geholfen, die einen k?nnen, die anderen lassen es einfach. Meiner Meinung nach stimmen der Name und dr QTH im QRZ.com zu weit ¨¹ber 90%, somit w?re f¨¹r mich ein nacharbeiten der restlichen paar % auf alle F?lle vertretbar.
Danke f¨¹r deine M¨¹he, so ein Programm zu schreiben und es den OM's zur Verf¨¹gung zu stellen.
vy 73 de Guntram OE9GWV


Re: Release 0.25

 

Hallo,

Entschuldigen Sie zun?chst mein Deutsch.
Obwohl ich ein wenig Deutsch verstehe, kann ich nicht richtig antworten. Deshalb habe ich Google Translator verwendet, um Ihnen antworten zu k?nnen. Daher hoffe ich, dass meine Antwort verst?ndlich ist.

Was Sie beschreiben, ist kein Fehler, sondern eine Funktion von QLog. QLog
speichert die Informationen, die es von WSJTX erh?lt. Der Name und QTH sind dort nicht enthalten. QTH und Name werden nur in QLog angezeigt. Ich hielt es f¨¹r nicht sinnvoll, dass QLog den QSOs zus?tzliche Informationen zur Verf¨¹gung stellt, die es von externen Programmen erh?lt. Dies liegt vor allem daran, dass die aus dem Callbook erhaltenen Informationen in Bezug auf das aktuelle QSO m?glicherweise nicht korrekt sind.

Es wird diskutiert, ob und welche Informationen f¨¹r QSOs von WSJTX automatisch hinzugef¨¹gt werden sollen. Das Einzige, was f¨¹r mich Sinn machen w¨¹rde, ist der Name des Betreibers. Die Korrektheit des QTH kann anhand der FT8/4-Verbindung nicht eindeutig bestimmt werden.

Ladislav


Re: Release 0.25

 

Hallo miteinander,
ich h?tte da mal eine Frage generell zu QLog. Ich sehe in der Auskunft den Namen und den QTH des Gegen¨¹bers, bekomme den aber dann nicht im Logbuch gespeichert, wo kann mein Fehler liegen. In Verwendung WSJT-Z, Gridtracker und eben QLog, das mir super gef?llt, wie es gemacht ist.
Vielen Dank im Voraus f¨¹r etwaige Ideen zur Probleml?sung
vy 73 de Guntram
OE9GWV


Release 0.25

 

Let me inform you that a new QLog release v0.23 is finished.

Changelog:
- [NEW] - Export - Added CSV Format
- [NEW] - Export - Added Type of Export Generic/QSLs
- [NEW] - Export - Added Exported Columns Setting
- [NEW] - Export - All export formats use the ADIF field name convention
- [CHANGED] - Export - JSON format contains a header - JSON format change
- [CHANGED] - Default Statistics Interval is curr_date-1 and curr_day
- Fixed Errors from Secure Storage are not shown
- Fixed RX/TX Bands are uneditable when RX/TX freqs are missing

Changelog:
Wiki:

Ladislav


Release 0.24

 

Let me inform you that a new QLog release v0.24 is finished.

Changelog:
- Fixed Incorrect FT4 mode-submode (issue #212)
- Fixed CONTESTIA mode should be CONTESTI (issue #213)
- Fixed Context menu deselects NewContactEditLine (issue #215)
- Fixed incorrect WSJTX Filter initialization (issue #218)

Ladislav


Release 0.23

 

Let me inform you that a new QLog release v0.23 is finished.

Changelog:
  • [NEW] - Added CWDaemon Keyer Support
  • [NEW] - Added FLDigi Keyer Support
  • [NEW] - Online Map - based on locale, the map language is selected (Only EN, FR, GE supported - issue )
  • Fixed After entering longer QTH, the field content is not left-aligned (issue )
  • Fixed wrong QSO Time in case of JTDX (issue )
  • Fixed QSL Sent Date fields are not filled if QSL Sent Status fields are Y (issue )


QSL Send Status

 
Edited

In the current version of QLog there is a special feature for the selection field "Paper" in the "QSL Send Status" in the "Detail Tab". Here always the last selection is used as default value for the following QSO's. Another variant would be to use here (only for paper QSL cards) a uniform default value "Yes", "No", ... to use.

What is the opinion of other QLog users about this.

73, Wolfgang
DL2KI


Release 0.22

 

QLog release v0.22 is out:
- [NEW] - ADIF Import - My Profile is used to define default values
- [NEW] - ADIF Import - Checking a minimal set of input fields (start_time, call, band, mode, station_callsign) - [NEW] - ADIF Import - Added Import Result Summary + Import Detail Info - [NEW] - Main Menu - Added Help -> Mailing List. - [NEW] - Export - Filter for the exported QSOs - [CHANGE] - Renamed Locator to Gridsquare - Fixed Some anomalies in the input and processing of QSLr Date (issue #192) - Fixed User unfriedly CW Keyer Error (issue #194) - Fixed ADIF import (issue #196) - Fixed Operator field is incorrectly used (issue #197) - Fixed Crash if an unknown POTA & SOTA/WWFF Setting is entered (issue #198) - Fixed FLDIGI cannot connect QLog (issue #199) - Fixed if ADIF record is missing band info, add this from freq field (thx DJ5CW)

Important Note: QLog misinterpreted the ADIF value "Operator". QLog used this field to store the operator name. The name of the operator is now stored in "MY_NAME". Automatic migration will not be performed. Please check impacted records (records created by QLog only, imported records are not affected) and manually edit the relevant records if necessary. Apologies for the inconvenience.

Windows Libraries: Qt 6.4.2
openssl 1.1.1t hamlib 4.4 qtkeychain 0.13.2

Timezone DB: 2023b (https://github.com/evansiroky/timezone-boundary-builder/releases)

Binaries:

Windows: https://github.com/foldynl/QLog/releases/download/v0.22.0/qlog-installer0.22.0.exe Fedora 36: (last) https://github.com/foldynl/QLog/releases/download/v0.22.0/QLog-0.22.0-1.fc36.x86_64.rpm Fedora 37: https://github.com/foldynl/QLog/releases/download/v0.22.0/QLog-0.22.0-1.fc37.x86_64.rpm Fedora 38: (new) https://github.com/foldynl/QLog/releases/download/v0.22.0/QLog-0.22.0-1.fc38.x86_64.rpm MacOS 12: https://github.com/foldynl/QLog/releases/download/v0.22.0/QLog-0.22.0_MacOs_dmg.zip Ubuntu 20.04, 22.04, 22.10 (last release), 23.04 (new): via PPA (https://launchpad.net/~foldyna/+archive/ubuntu/qlog)