Stocking
Stocking
I see that frequencies are handled internally as a `double` representing megahertz. This may be bad form and open to interpretation. Someone might be under the assumption that those doubles...
Will come back later to add more text info regarding this. I clicked "add" trying to log a fake QSO for debugging purposes. And then this happened:  Maybe the...
Klog has some memory issues. There's a double `free()` somewhere and valgrind has a field day listing off issues. Traditional unsafe C-style pointers are used throughout the codebase, even in...
I suppose the code style describing brackets/spaces/tabs/etc was either never there or was deleted. See here: https://github.com/ea4k/klog/blob/d308f9862ddb2f3895f3c6f7452f2327f94ea83e/src/README-DEVEL#L133-L134 Suggestions: 1. Move `README-DEVEL` and any other text files out of `/src/` and...
This isn't clearly readable and probably isn't conform accessibility standards. No idea what's going on here. I'm using cinnamon and dark mode. 
Include guard name collisions are no fun to debug. The core cpp guidelines recommend a 'good discriminator'. https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines#sf8-use-include-guards-for-all-header-files Since paths are unique, I recommend the following syntax: `KLOG_PATH_TO_FILE_H` | `#define...
When using hamlib + flrig for IC-7300 rig control, klog seems to naively track VFO A frequency. Even when rig is using VFO B or when enabling split on the...
This fixes #726
Steps to enable bug: 1. Go to settings 2. Enable darkmode by pressing the "Darkmode" button once 3. Observe program correctly switching to darkmode theme. 4. Press "OK". 5. Observe...
There are no `qDebug()` messages appearing in that file yet the timestamp is clearly updated so the file is opened. The file is empty even while klog is still running...