From time to time some people ask me to push my code to GitHub.
I must admit that I am confortable having KLog in the Savannah SVN. It works without any error, not a simngle problem since I started to use it many years ago, I also have some automations built at home, in my development environment… I though that it made no sense to migrate to GitHub.
Some days ago I decided to move my code to GitHub, I will probably keep Savannah and GitHub repositories until (hopefully) I finally get the same feeling with GitHub than Savannah.
I am doing this with the hope that some of you will be contributing to KLog easily if it is in GitHub and maybe KLog improves 🙂
If KLog development is mainly mine, it makes no sense to move to GitHub.
If you want to contribute, register with your callsign and send me an email so I can change your profile to the editor profile… yes, it is not done automatically but I prefer to go this way to have the wiki full of spam in some days.
I will work on the wiki, trying to explain how to use KLog and I will also try to not releasing a new feature that is not explained I the Wiki.
KLog 1.4 has been released. This relased has been possible after a lot of testing and bug fixing (Thank you for all the testers!)
This version of KLog is a quite interesting one as it adds support for online services like LoTW, QRZ.com, ClubLog and eQSL.cc. It is still basic level but it will allow you to: – Upload & download your QSL confirmations to LoTW. – Check for calls in QRZ.com and fill your QSOs automatically. – Upload your log to QRZ.com, ClubLog and eQSL.cc.
WSJT-X will update how QSOs are sent to the loggers in its next version and KLog is already prepared for it.
In addition, many bugs have been fixed.
The Changelog shows:
- Improvement: Prepared the WSJTX-2.4 UDP interface.
- Improvement: User data stored in the setup is know used in the QSOs (default power, station callsign).
- Improved the KG4xx (Guantanamo bay) DXCC detection from KG4 calls.
- Updated how KLog counts the confirmed DXCC entities to include LoTW confirmations.
- New feature: QSO upload to the QRZ.com Logbook (including qso selection and qso mark that has been uploaded)
- New feature: QSO upload to the eQSL.cc Logbook (including qso selection and qso mark that has been uploaded)
- New feature: ClubLog full log upload (adding or overwriting).
- New feature: It is possible to keep the comment field from one QSO to the following one. (TNX EA5WA)
- New feature: It is possible to select multiple QSOs in the log and execute several actions with the selected QSOs.(TNX EA5WA)
- New feature: It is possible to check for the data of calls in QRZ.com (you need a subscription in QRZ.com)
- UI: Removed the Keep my data option from the Setup UI.
- UI: The RX frequency follows the TX unless the split is checked.
- UI: Consolidation of all the electronic logs configurations in one single setup page into the eLog tab.
- Bugfix: Save all QSOs to ADIF process continued even if the user clicked in cancel.(TNX G4MKT)
- Bugfix: Backup file was not being created in the right path.(TNX G4MKT)
- Bugfix: Some paths were converted to upper case causing some issues in some case sensitive situations. (TNX G4MKT)
- Bugfix: In some cases, the RST format was not properly defined.(TNX G4MKT)
- Bugfix: Default ADIF file was not being saved on exit. (TNX G4MKT)
- Bugfix: It was not possible to select empty logs from the preferences. (TNX G4MKT)
- Bugfix: QSOs comming from WSJTx were not being uploaded to ClubLog. (TNX PD9Q)
- Bugfix: Too many mesages when uploading in realtime to Clublog. It should be done silently.(TNX EA5WA)
- Bugfix: Typo in the INSTALL-linux. (TNX DL4TO)
- Bugfix: Hamlib polling rate was not being saved from the setup. Default value is defined to 300ms. (TNX G4MKT)
- Bugfix: Complete with previous QSO (name, locator, ...) was not working properly.
- Bugfix: PROGRAMID ADIF data was not properly tagged.
- Bugfix: When selecting the QSOs to upload to LoTW, if the selected call was the first one on the combobox, selection didn't worked properly.
- Bugfix: When importing ADIF files with fields without RST_SENT or RST_RCVD the proposed default value was not adapted to the mode of that QSO.
- Bugfix: Extension .adi was always added, even if the file had it already.
- Bugfix: When doing a database backup, the name of the file was not being properly defined.
- Bugfix: ClubLog realtime syncronization was not working properly.
I have just released KLog 1.3. The main new feature is a great optimization in the search engine that allows to search very quickly even in big logs.
You can see the Changelog to check what other improvements and bugfixes are coming with KLog 1.3.
KLog 1.3.1 is also including the Croatian translation.
October – 1.3.1
– Translations: Croatian (TNX M0NKC).
October – 1.3
– Improved the search widget to make searching much quicker.
– Improved the Edit of QSO related to the default QSL sent status.
– Improved the QRZ.com & DXHeat.com queries from the log & search window.
– Improved the UDP datagram receiver to ensure it is working multicast.
– UI: KLog remembers the size of the window from last execution. (TNX EA5WA)
– UI: The Station Callsign and number of QSOs in the current log is shown in the windows title.(TNX G4MKT)
– New feature: KLog now search for the call as the user enters for previously QSOs with that call. (TNX EA5WA)
– Adds an “.adi” file extension to the log ADIF files if not added by the user. (TNX G4MKT)
– When reading a log from LoTW, if there are new QSOs not present on the current logfile, KLog offers the option to import them.
– Bugfix: It was not possible to add a log if the date and Station Callsign were the same. Now operators and comments are also taken into consideration.(TNX G4MKT)
– Bugfix: The export of QSOs without an station callsign defined was failing.(TNX G4MKT)
– Bugfix: When reading a log from LoTW, the list of QSOs were not shown at the end. (TNX EA5WA)
– Bugfix: Comment in the new log widget was converted to uppercase. (TNX G4MKT)
– Translations: Catalan (TNX Txema), Italian (TNX IU5HIU), Spanish (EA4K).
As previous times, after a release, with new features, there is a bugfix release.
Today I am releasing 1.2.1 that arrives after some days of development during holiday time 🙂
This kind of releases never come with new features but with bugfixes and improvements. I really recommend to update to this release.
This is the Changelog:
Aug 2020 - 1.2.1
- Bugfix: ADIF export was not exporting dates with the right format in some eQSL fields.
- Bugfix: QSOs were not properly imported when received from WSJT-X.
- Bugfix: Pool/Poll typo fixed. (TNX Barry!).
- Bugfix: QSO editing - Locator was being cleared from sat tab.
- Bugfix: QSO editing - User Inferface was not properly clearedn after editing.
- Bugfix: QSOs tag in the Award tab was not properly formatted in Windows OS.
- Improvement: ADIF creation has been optimized.
- Improvement: All fields received from WSJTX are now added to the log.
- Improvement: GRIDSQUARE & MY_GRIDSQUARE ADIF fields are now also exported to LoTW upload.
Maintaining a free software application where you simply code and upload your packages to the repositories makes very difficult to know if is there somebody out there using what you are producing.
I started KLog not for the users but for personal use and I keep that spirit, however the users of KLog are important as some of them are actively supporting KLog by reviewing, reporting bugs, providing suggestions, patchs, translations and I have even received some donations that I have used to pay for the hosting 🙂
On the other hand, I guess that the users that are actively saying “hello I am here” are just a small percentage.
It would be really interesting to have similar data coming from other sources, to see if one of the main differences of KLog (being native multiplatform) is noticed or not. How many macOS users does KLog have? How many Windows users does KLog have?
Anyway, these data are just for information and I hope it is funny for you to see what the popcon package is providing as it was for me to write this post.
Este sitio web utiliza cookies para que usted tenga la mejor experiencia de usuario. Si continúa navegando está dando su consentimiento para la aceptación de las mencionadas cookies y la aceptación de nuestra política de cookies, pinche el enlace para mayor información.plugin cookies
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.