ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
esc to dismiss
Re: Feature request: Clock setting toggle. (take a moment, hear me out)
Please explain this to me. My approach is that I want all applications to be "unified". This means that if I want a 24h time-format, I want to see it in all my installed applications. Why is your approach that you want to see applications in 12h-format, but QLog in 24h?
To be honest, the change is trivial in QLog. We are talking more about it here than it would mean to change it. For me, it is more important to understand this difference. After all, this problem is not only about the 12/24 format, but about the whole date/time formatting. p¨¢ 10. 1. 2025 v?20:11 odes¨ªlatel Michael Morgan via <cmorgan13= [email protected]> napsal:
I agree that is one the few things that is awkward with the app for me.? I would like for the app to show 24 hour UTC time everywhere - log entries, clock etc. ?but I don't really?want my whole mac showing 24 hour time, guess I'm just to lazy to have to math the times since I use it not only for ham tasks.? I've been trying to work out a script?to launch different things (rigctld so I can share my radio with QLog and other apps, do commands so WSJT laucnhes happy and also my steppir/amp controller apps, etc.) So I could technically put the LC command in there but since last step currently is to launch rigctld since it holds the terminal I wouldn't be able to then launch QLog so it would take the LC command.? I'm sure there maybe a way in applescript to launch it or launch multiple ?terminals or something.? Got to figure that out.
On Fri, Jan 10, 2025 at 10:09?AM Kevin Loughin via <loughkb= [email protected]> wrote: I am a youtube presenter that does mostly ham radio videos.? As such, through comments on my videos, I have a good impression of the general audience technical abilities.
?
That said,? I recently reviewed Qlog,? my new favorite logging software and I love it.? The perfect balance between features and simplicity.
?
In my recent post about the clock and 24 hour time, one response pointed me to the wiki tip about setting an LC system variable to get the program to display 24 hour time.? Thank you, that solved MY problem.? However, I can state with confidence that the majority of the potential user base for this program are not at the skill level or competency required to be digging around in system configuration files and setting system variables.
?
So, I would like to request a simple preference setting,? a toggle between local and UTC time.? In local mode, the clock would behave as it does now, basing it's display on the local system settings.? In UTC mode, the clock would display 24 hour time and align it's offset to UTC.??
This could either be a setting in the preferences panel, or, ideally, a widget within the clock panel itself, allowing the user to toggle the time format as needed depending on their operating environment at the time.
?
This would enhance the intuitiveness of the interface with regard to the clock display, and work for the entire potential user base.
?
Thanks for any consideration,
Kevin - KB9RLW
|
I¡¯ve uploaded the MacOS build:
|
toggle quoted message
Show quoted text
On Jan 11, 2025, at 3:24?AM, ok1mlg via groups.io <ok1mlg@...> wrote:
Let me inform you that a new QLog release v0.41.0 is finished.
Changelog:
- [NEW] - Logbook - Added a new context menu item - Update QSO from Callbook (issue #450 @aa5sh)
- [NEW] - DIGI mode is used in case of DXC Digi Spots (issue #480)
- [NEW] - DXC - Retrieve information about SOTA, POTA, IOTA and WWFF from comment (issue #482)
- [NEW] - Alert - Added SOTA, POTA, IOTA and WWFF filter
- [NEW] - Added the COM Port Completer for Windows platform (issue #490)
- [NEW] - Settings - Added DXCC Confirmed By options (issue #508)
- [NEW] - Added POTA Export Formatter (activator/hunter) (PR #514 @kyleboyle)
- [NEW] - CW Console - CW Halt with the user-defined shortcut (issue #518)
- [NEW] - Added an input parameter to save debug message to file
- [NEW] - Logbook - Added sorting function to logbook table columns (PR #540 @kyleboyle)
- [NEW] - Network Notification - Added Rig Status Notification
- [NEW] - Implemented ADIF 3.1.5
- [NEW] - ADIF 3.1.5 - Added new submodes FSKH245 and FSKH105 for HELL
- [NEW] - ADIF 3.1.5 - Added new contest IDs
- [NEW] - ADIF 3.1.5 - Added new columns (Import/Export only)
- [NEW] - ADIF 3.1.5 - Added My DARC DOK to Station Profile
- [CHANGED] - Settings: disabled band and mode name modification
- [CHANGED] - DX Stats contain all enabled bands (issue #538)
- [CHANGED] - Removed Freq, TimeDate On/Off Data Type Indicators (issue #552)
- [CHANGED] - ADIF 3.1.5 - VUCC and MY_VUCC can contain 6 or 4-chars locators
- [CHANGED] - Stop exporting default value N for qsl_rcvd, qsl_sent, lotw/dcl/eslq_qsl_rcvd/sent
- [CHANGED] - Extended QSL/Import Dupe matching rule to Callsign, Band, Mode, Time and Sat_Name (issue #563)
- Fixed MacOS - keep floating windows visible on app unfocus (issue #530)
- Fixed Contest Filter ignores the first QSO (issue #529)
- Fixed It is not possible to quit Qlog with detached widgets Rot & Rig (issue #534)
- Fixed ADX/CSV/JSON do not export non-ASCII chars (issue #542)
- Fixed Checking the 60m checkbox in cluster filters allows 160m spots to appear (issue #543 @aa5sh)
- Fixed Problems uploading to QRZ.com (issue #559 PR #561 @aa5sh)
- Fixed DX Stat screen is jumping up/down
- Fixed Omnirig drivers: Digi modes are not correctly recognized
HAMLIB Upgrade
- Windows and Flatpak packages now include Hamlib v4.6.
Changelog:
Wiki Changelog:
Let me inform you that a new QLog release v0.41.0 is finished.
Changelog:
- [NEW] - Logbook - Added a new context menu item - Update QSO from Callbook (issue #450 @aa5sh)
- [NEW] - DIGI mode is used in case of DXC Digi Spots (issue #480)
- [NEW] - DXC - Retrieve information about SOTA, POTA, IOTA and WWFF from comment (issue #482)
- [NEW] - Alert - Added SOTA, POTA, IOTA and WWFF filter
- [NEW] - Added the COM Port Completer for Windows platform (issue #490)
- [NEW] - Settings - Added DXCC Confirmed By options (issue #508)
- [NEW] - Added POTA Export Formatter (activator/hunter) (PR #514 @kyleboyle)
- [NEW] - CW Console - CW Halt with the user-defined shortcut (issue #518)
- [NEW] - Added an input parameter to save debug message to file
- [NEW] - Logbook - Added sorting function to logbook table columns (PR #540 @kyleboyle)
- [NEW] - Network Notification - Added Rig Status Notification
- [NEW] - Implemented ADIF 3.1.5
- [NEW] - ADIF 3.1.5 - Added new submodes FSKH245 and FSKH105 for HELL
- [NEW] - ADIF 3.1.5 - Added new contest IDs
- [NEW] - ADIF 3.1.5 - Added new columns (Import/Export only)
- [NEW] - ADIF 3.1.5 - Added My DARC DOK to Station Profile
- [CHANGED] - Settings: disabled band and mode name modification
- [CHANGED] - DX Stats contain all enabled bands (issue #538)
- [CHANGED] - Removed Freq, TimeDate On/Off Data Type Indicators (issue #552)
- [CHANGED] - ADIF 3.1.5 - VUCC and MY_VUCC can contain 6 or 4-chars locators
- [CHANGED] - Stop exporting default value N for qsl_rcvd, qsl_sent, lotw/dcl/eslq_qsl_rcvd/sent
- [CHANGED] - Extended QSL/Import Dupe matching rule to Callsign, Band, Mode, Time and Sat_Name (issue #563)
- Fixed MacOS - keep floating windows visible on app unfocus (issue #530)
- Fixed Contest Filter ignores the first QSO (issue #529)
- Fixed It is not possible to quit Qlog with detached widgets Rot & Rig (issue #534)
- Fixed ADX/CSV/JSON do not export non-ASCII chars (issue #542)
- Fixed Checking the 60m checkbox in cluster filters allows 160m spots to appear (issue #543 @aa5sh)
- Fixed Problems uploading to QRZ.com (issue #559 PR #561 @aa5sh)
- Fixed DX Stat screen is jumping up/down
- Fixed Omnirig drivers: Digi modes are not correctly recognized
HAMLIB Upgrade
- Windows and Flatpak packages now include Hamlib v4.6.
Changelog:
Wiki Changelog:
|
Re: Feature request: Clock setting toggle. (take a moment, hear me out)
I agree that is one the few things that is awkward with the app for me.? I would like for the app to show 24 hour UTC time everywhere - log entries, clock etc. ?but I don't really?want my whole mac showing 24 hour time, guess I'm just to lazy to have to math the times since I use it not only for ham tasks.? I've been trying to work out a script?to launch different things (rigctld so I can share my radio with QLog and other apps, do commands so WSJT laucnhes happy and also my steppir/amp controller apps, etc.) So I could technically put the LC command in there but since last step currently is to launch rigctld since it holds the terminal I wouldn't be able to then launch QLog so it would take the LC command.? I'm sure there maybe a way in applescript to launch it or launch multiple ?terminals or something.? Got to figure that out.
On Fri, Jan 10, 2025 at 10:09?AM Kevin Loughin via <loughkb= [email protected]> wrote: I am a youtube presenter that does mostly ham radio videos.? As such, through comments on my videos, I have a good impression of the general audience technical abilities.
?
That said,? I recently reviewed Qlog,? my new favorite logging software and I love it.? The perfect balance between features and simplicity.
?
In my recent post about the clock and 24 hour time, one response pointed me to the wiki tip about setting an LC system variable to get the program to display 24 hour time.? Thank you, that solved MY problem.? However, I can state with confidence that the majority of the potential user base for this program are not at the skill level or competency required to be digging around in system configuration files and setting system variables.
?
So, I would like to request a simple preference setting,? a toggle between local and UTC time.? In local mode, the clock would behave as it does now, basing it's display on the local system settings.? In UTC mode, the clock would display 24 hour time and align it's offset to UTC.??
This could either be a setting in the preferences panel, or, ideally, a widget within the clock panel itself, allowing the user to toggle the time format as needed depending on their operating environment at the time.
?
This would enhance the intuitiveness of the interface with regard to the clock display, and work for the entire potential user base.
?
Thanks for any consideration,
Kevin - KB9RLW
|
Feature request: Clock setting toggle. (take a moment, hear me out)
I am a youtube presenter that does mostly ham radio videos.? As such, through comments on my videos, I have a good impression of the general audience technical abilities.
?
That said,? I recently reviewed Qlog,? my new favorite logging software and I love it.? The perfect balance between features and simplicity.
?
In my recent post about the clock and 24 hour time, one response pointed me to the wiki tip about setting an LC system variable to get the program to display 24 hour time.? Thank you, that solved MY problem.? However, I can state with confidence that the majority of the potential user base for this program are not at the skill level or competency required to be digging around in system configuration files and setting system variables.
?
So, I would like to request a simple preference setting,? a toggle between local and UTC time.? In local mode, the clock would behave as it does now, basing it's display on the local system settings.? In UTC mode, the clock would display 24 hour time and align it's offset to UTC.??
This could either be a setting in the preferences panel, or, ideally, a widget within the clock panel itself, allowing the user to toggle the time format as needed depending on their operating environment at the time.
?
This would enhance the intuitiveness of the interface with regard to the clock display, and work for the entire potential user base.
?
Thanks for any consideration,
Kevin - KB9RLW
|
My solution was to set the laptop to 24hr UTC time and add a
timezone clock to the task bar and set it to local time.
V/R,
Michael G. McGuire, K3SNO
484-703-9591
So Mote It Be.
On 1/9/25 15:17, Kevin Loughin via
groups.io wrote:
toggle quoted message
Show quoted text
Hello,?
?
? ?Running Ubuntu mate, current version. Installed Qlog via
flat pack and all is well except the clock is stuck in 12 hour
am/pm mode.? I've searched through the wiki and here, but don't
find any advice. I have set my system time to 24 hour format,
and my desktop clock indicates in 24-hour format. (In recent
versions of the mate desktop, you cannot set it one way or the
other, it mirrors the system setting.).?
Q log still shows an AM/PM clock. I haven't found a setting
anywhere. Is there a flag on launch that can switch it to
24-hour??
?
DE, KB9RLW.
|
Qlog performs the automatic export as it is described on . It is done before the start and according to the plan as written on wiki. There is nothing simpler than making your own script that copies backup files where you need it, or you don't even have to do anything if you have your home directory automatically backed up.
Automatic export of the ADI file, each time the program is closed, to an external storage device such as a USB Flash Drive, USB HD, etc¡.
|
I can't be a lot of help with Linux. ?But I know it should be driven by OS Settings. ?Some basic info is here in the wiki:
On my Mac I can change the '24-Hour Time' settings in preferences and it does adjust it.
?
?
Not a great example due to the time now but you can see the AM drop off and the leading zero.
?
Michael, AA5SH
|
Automatic export of the ADI file, each time the program is closed, to an external storage device such as a USB Flash Drive, USB HD, etc¡.
|
Hello,?
?
? ?Running Ubuntu mate, current version. Installed Qlog via flat pack and all is well except the clock is stuck in 12 hour am/pm mode.? I've searched through the wiki and here, but don't find any advice. I have set my system time to 24 hour format, and my desktop clock indicates in 24-hour format. (In recent versions of the mate desktop, you cannot set it one way or the other, it mirrors the system setting.).?
Q log still shows an AM/PM clock. I haven't found a setting anywhere. Is there a flag on launch that can switch it to 24-hour??
?
DE, KB9RLW.
|
|
|
One click solution for 'service' uploads for any/all on-line QSL services that are configured.
?
WW4DX
|
Re: Map projection is wrong?
Also if you'd prefer to not subscribe to qrz (which lists EN71LD as his grid square), you could use hamqth which is free, and get potentially fewer hits and less granular grid squares at times (his is listed as EN71).
|
Re: Map projection is wrong?
QLog shows the path based on the Grid information. If there is no grid then QLog shows the path to the center of the DXCC Entity. This means that if you do not specify a grid, it will show the center of the US. To
get the Grid from , you must have at least the XML subscription
Please, see
for more detail
Regards Ladislav
so 4. 1. 2025 v?17:24 odes¨ªlatel Kevin Loughin via <loughkb= [email protected]> napsal:
[Edited Message Follows]
As requested, here are some screenshots.? ?Things I notice,? I'm in the U.S., ITU region 2, yet it insists on assigning me and the Indiana call I entered to ITU region 8?? I manually changed ITU to 2 in my station settings.? ?Also, it's pulling some of his info from QRZ, but not populating his grid square.?? The plot on the map is always exactly the same, regardless of what call I enter in the log entry.? The start of the plot is also wrong, it's starting at the west edge of the grid square and state, I'm more slightly to the left of center of that area.   
|
Re: Map projection is wrong?
As requested, here are some screenshots.? ?Things I notice,? I'm in the U.S., ITU region 2, yet it insists on assigning me and the Indiana call I entered to ITU region 8?? I manually changed ITU to 2 in my station settings.? ?Also, it's pulling some of his info from QRZ, but not populating his grid square.?? The plot on the map is always exactly the same, regardless of what call I enter in the log entry.? The start of the plot is also wrong, it's starting at the west edge of the grid square and state, I'm more slightly to the left of center of that area.   
|
Re: Map projection is wrong?
Hi Kevin, could you provide screenshots of your station information which is active for the qso log, the qso call entry (and the auto-populated remote station's grid square, typically in your field rows or details tab) and the resultant map render.
Thanks,
Kyle
|
Re: Map projection is wrong?
Hey Kevin, Can you send a screenshot of what you are seeing?? I'm curious if you are seeing the online or offline maps.? If offline I wonder if it may be skewed if you have any sort of scaling on your monitor.? I've not used the offline version so I'm not very experienced on it.? I also use the MacOS version. Here is a snip of the online maps when I open a recent QSO.
Howdy,
? I just installed and configured Qlog and I'm impressed.? Running on the latest Ubuntu mate version and I installed via flathub.? Everything seems to be working well except the map.? ?
? I entered my first contact, a station up in Oregon.? I am in Kingman AZ.? I've put my data in under my station profile, including my grid square.? For this contact, the map is plotting a line from far western AZ, west of my location, to somewhere in Kansas and showing 1,200 miles when the actual plot should go north to Oregon, a significantly shorter distance.??
?
? I entered another call and again, the plot on the map was way off.? I'm at a loss as to why.? Any pointers?? I need to get this sorted so I can complete my youtube review of the program.
?
Kevin, KB9RLW
|
Re: #featurerequest in statistic page the number of medium grid square (like JN35) and big square (JN)
#featurerequest
Hello,
That's worth considering.
I opened an Github issue for it -
Regards Ladislav
Hi,
?
The map is nice to show the worked big or medium squares but the is no counter to say 128 big squares worked on 10m and? 56 on 6m ...
and same for medium squares.
Perhaps in the statistics page.
?
73
F1RAD
|
Re: A way to update LOTW and eQSL details?
I think it would be good to consider importing the details if enough matches, like Callsign, band, date, time, and IF LoTWr and LoTWr Date are empty, then import it.? Or same for Send, or eQSL.
On Mon, Dec 30, 2024 at 10:17?PM Michael Morgan via <cmorgan13= [email protected]> wrote: Ok in looking at the code if I am understanding it QLog will update information from LoTW if it is empty (the dates, grid, credit, iota etc) but only if it is the first time setting the lotw qsl received flag to a Yes.? Maybe Ladislav can validate me on that. ?
I¡¯m not sure if we want to consider an option to have it update the log with data from LoTW QSL records if the other empty no matter what?? Maybe have an option on the LoTW QSL Service window?? I don¡¯t think it should be the default but maybe be an option in case someone like you wants to do it initially if they are moving from another logbook that doesn¡¯t keep all that data the same?
It would be pretty easy to add a checkbox that would alter that check for the ¡®Yes¡¯. But I also know the goal of QLog is to keep things simple but powerful so any options like this need to be considered before adding.
Michael
On Dec 30, 2024, at 8:52?PM, Joel Vazquez, WE0DX via <ae4sr.radioop= [email protected]> wrote:
I was looking for a way, if possible, to update not only the LoTWr/s fields, but also the dates for them (LoTWr/s Date fields).
On Mon, Dec 30, 2024 at 1:39?PM Michael Morgan via ??<cmorgan13= [email protected]> wrote: If you want to bulk edit QSOs you can easily change all of the N for LoTWs?to a Y.? Just add that column to your log view by right clicking on the header row or right click on a field and select 'Column Visibility' and add LoTWs: <image.png>
Once added you can select all rows then right click on LoTWs?- N row and hit 'Edit Value'.? <image.png>
From there if you change it to Y it will prompt if you want to change it for all selected rows.
Michael, AA5SH
On Mon, Dec 30, 2024 at 11:02?AM Joel Vazquez, WE0DX via ??<ae4sr.radioop= [email protected]> wrote: Sorry, I should have explained better the intention, yes I want to update confirmed status from old contacts.? I'm sure they were updated before on my previous log software, but it seems that when importing those were maybe miss importing the values.? I tried the option under Services, adjusting my callsign and dates, but it didnt update all the old contacts.??
For example, look at this screenshot:
<image.png>
The log (in the right background) shows the contact that I "received" the LoTW, but marks that I didn't send it.? That's not logical since to be able to receive (or show that you received) the qsl, LoTW service requires you to upload your contact and IF it matches it shows you your received qsl.? And in fact, as you can see on the left side of the screenshot, I did upload it.? So it's a matter of updating it, but that's the question, what's the best safest way (after doing a log backup :D)....? I dont want to re-upload everything and duplicate it on LoTW or eQSL.
Thanks,
On Sun, Dec 29, 2024 at 8:05?PM Michael Morgan via ??<cmorgan13= [email protected]> wrote: Are you just wanting to get the confirmed status for LoTW?? Or adjust other QSO details like maybe missing counties or whatever? ?
if just confirmations you can use the LoTW option under services and there is an option to down load QSLs which will update the flags. ? Michael, AA5SH
|
Re: A way to update LOTW and eQSL details?
Ok in looking at the code if I am understanding it QLog will update information from LoTW if it is empty (the dates, grid, credit, iota etc) but only if it is the first time setting the lotw qsl received flag to a Yes. ?Maybe Ladislav can validate me on that. ?
I¡¯m not sure if we want to consider an option to have it update the log with data from LoTW QSL records if the other empty no matter what? ?Maybe have an option on the LoTW QSL Service window? ?I don¡¯t think it should be the default but maybe be an option in case someone like you wants to do it initially if they are moving from another logbook that doesn¡¯t keep all that data the same?
It would be pretty easy to add a checkbox that would alter that check for the ¡®Yes¡¯. But I also know the goal of QLog is to keep things simple but powerful so any options like this need to be considered before adding.
Michael
toggle quoted message
Show quoted text
On Dec 30, 2024, at 8:52?PM, Joel Vazquez, WE0DX via groups.io <ae4sr.radioop@...> wrote:
I was looking for a way, if possible, to update not only the LoTWr/s fields, but also the dates for them (LoTWr/s Date fields).
On Mon, Dec 30, 2024 at 1:39?PM Michael Morgan via ??<cmorgan13= [email protected]> wrote: If you want to bulk edit QSOs you can easily change all of the N for LoTWs?to a Y.? Just add that column to your log view by right clicking on the header row or right click on a field and select 'Column Visibility' and add LoTWs: <image.png>
Once added you can select all rows then right click on LoTWs?- N row and hit 'Edit Value'.? <image.png>
From there if you change it to Y it will prompt if you want to change it for all selected rows.
Michael, AA5SH
On Mon, Dec 30, 2024 at 11:02?AM Joel Vazquez, WE0DX via ??<ae4sr.radioop= [email protected]> wrote: Sorry, I should have explained better the intention, yes I want to update confirmed status from old contacts.? I'm sure they were updated before on my previous log software, but it seems that when importing those were maybe miss importing the values.? I tried the option under Services, adjusting my callsign and dates, but it didnt update all the old contacts.??
For example, look at this screenshot:
<image.png>
The log (in the right background) shows the contact that I "received" the LoTW, but marks that I didn't send it.? That's not logical since to be able to receive (or show that you received) the qsl, LoTW service requires you to upload your contact and IF it matches it shows you your received qsl.? And in fact, as you can see on the left side of the screenshot, I did upload it.? So it's a matter of updating it, but that's the question, what's the best safest way (after doing a log backup :D)....? I dont want to re-upload everything and duplicate it on LoTW or eQSL.
Thanks,
On Sun, Dec 29, 2024 at 8:05?PM Michael Morgan via ??<cmorgan13= [email protected]> wrote: Are you just wanting to get the confirmed status for LoTW?? Or adjust other QSO details like maybe missing counties or whatever? ?
if just confirmations you can use the LoTW option under services and there is an option to down load QSLs which will update the flags. ? Michael, AA5SH
|
Mike - K3SNO, #707
WW4DX
Joel Vazquez, WE0DX