KLog is a multiplatform free hamradio logger, the only one able to run in Linux, Windows and macOS!
KLog is providing QSO management, useful QSL management DX-Cluster client, DXCC management, ClubLog integration, WSJT-X, DX-Marathon support and much more!
KLog is today already in several languages: Catalan, Croatian, Danish, English, Finish, Italian, Japanese and Spanish.
You can also see some Screenshots of KLog to see what it looks like.
There is one main new feature and some other minor topics.
From KLog 0.9.7 you will be able to add, remove or edit satellites to the KLog DB and you will also be able to import or export satellites data lists.
The other thing that you will be able to do from now, it is to disable the DX-Marathon support. Some of the KLog users are not DX-Marathon followers and it is very convenient to be able to get rid of the DX-Marathon status, specially in the DX-Cluster!
As always, this is the changelog:
March – 0.9.7
Bugfix: When clicking on Check updates, the dialog froze.
Bugfix: Printing log is not longer showing band in the mode column.
Updated the default date on date boxes to the current date.
Improved the Frequency syncronization between Satellite tab and the main tab.
Improved how default mode is calculated.
Added Satellites widget in Setup.
Updated translations: Catalan (TNX Txema), Danish (TNX Joe), Finnish (TNX Kristjan), French (F4HWL), German (TNX Burkhard), Spanish (EA4TV).
Please wait some time if the browser returns a file not found error. It may be caused due to the mirrors need to update. The process could take up to 24h!
This is a very quick release due to a bug that was found some days ago and I have decided to fix and relase as soon as possible.
The changelog shows:
December 2018 – 0.9.6
– Optimizing the Statistics widget.
– Added some new Statistics widgets.
– Fixed some messages with typos.
– Bugfix: Fixed a bug preventing to modify a QSO. (TNX KB2YSI).
Several people have collaborated in this relase, from translators to testers, to people doing sugestions or working on the new sats.dat file. Thank you all!
KLog 0.9.5 brings two new interesting features and two new languages:
Statistics of your log (that you can use in the Tools->Stats menu).
Satellite data Update (Tools->Update Satellite Data). With this you will be able to update the satellites data when there is a new satellite inthe sky or we have detected an error in the current data. I will post here the new new sats.dat file releases. (TNX KB2YSI!).
Murphy has came to KLog 0.9.4 and just after releasing, I found a bug.
Not too important, no data was lost and everything worked OK but the message that was shown to the user when a QSO was coming from WSJT-X was incorrect as the operator callsign was not properly parsed from the WSJT-X data.
Being a release that is mainly focused to WSJT-X… I decided to fix it ASAP.
Anyway, I have just released 0.9.4.1 with that bugfix only.
As always, you can download from the repositories.
KLog 0.9.4 is finally here and it brings one interesting new feature and one important bugfix.
Now it is possible to send QSO data directly from WSJT-X to KLog and KLog will update it in the QSO entry or log the QSO sent from WSJT-X.
It will really save time for those of us using WSJT-X!
In addition the translations for Catalan, Croatian, Danish, Spanish and of course English, have been fully updated.
Find below the Changelog.
August 2018 – 0.9.4
WSJT-X support to receive logged QSO and realtime data.
Check bool DataBase::updateTo012() / it was always returning true without any action.
Syncronize RX Freq with the satellite downlink combobox.
Focus is back to search line edit when right click on the list of found QSOs.
Update process has been improved.
Some warnings removed from compilation time.
Bugfix: Date was not properly calculated and UTC settings was not applied. That may create wrong date QSO when date changes due to UTC (TNX AC1DW).
Bugfix: When adding a QSO, if the QSL is marked as received, KLog showed a SQL error.
Bugfix: Table qsl_via needed to be renamed (TNX EA6ZS).
Bugfix: Some DXCC status were nor properly calculated.
Please wait some time if the browser returns a file not found error. It may be caused due to the mirrors need to update. The process could take up to 24h!
