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

On Sat, Jan 11, 2025 at 9:43 AM, ok1mlg via groups.io

<ok1mlg@...> wrote:

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

What I have learned in dealing with the larger audience, and also through my working career in computer support in large companies, is that everybody has their own preferences. There is no one "right" way to do anything with a few exceptions.?

You want all of your applications to behave the same with this regard.? Myself, I would like most of my other applications to operate on local 12 hour time. But my ham radio applications to operate on UTC time. I suspect, from my interactions with others, that this is perhaps the more common scenario.?

In either case, flexibility within the application merely broadens its appeal and increases its level of comfort across the broader audience. Giving the user the choice, improves the acceptance and appreciation of the program.?

That's my two cents worth.?

Kevin?

On Sat, Jan 11, 2025 at 9:43 AM, ok1mlg via

<ok1mlg=[email protected]> wrote:

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

On Sat, Jan 11, 2025 at 12:38 PM, Michael Morgan via groups.io

<cmorgan13@...> wrote:

I know for me it is I use my laptop for both Ham and work/personal.? I just prefer for my normal life just to be 12 hour.? But for ham everything is typically?in 24hr, QSL, contests etc.? So it is just an ease of use thing.

On Sat, Jan 11, 2025 at 1:31?PM ok1mlg via <ok1mlg=[email protected]> wrote:

OK. Flexibility is a good thing but excessive flexibility is counterproductive. The average user isn't capable of foreseeing all the things they could break with various settings. I'm not talking about time format settings specifically here, but more generally about the ability to configure everything in the applications.

But you didn't answer my question. Why do you require a 24-hour format specifically in the ham application, when you use a 12-hour format for everything else? I'm not criticizing you; I'm just very curious because it could guide my future steps.

so 11. 1. 2025 v?18:48 odesílatel Kevin Loughin via <loughkb=[email protected]> napsal:

What I have learned in dealing with the larger audience, and also through my working career in computer support in large companies, is that everybody has their own preferences. There is no one "right" way to do anything with a few exceptions.?

You want all of your applications to behave the same with this regard.? Myself, I would like most of my other applications to operate on local 12 hour time. But my ham radio applications to operate on UTC time. I suspect, from my interactions with others, that this is perhaps the more common scenario.?

In either case, flexibility within the application merely broadens its appeal and increases its level of comfort across the broader audience. Giving the user the choice, improves the acceptance and appreciation of the program.?

That's my two cents worth.?

Kevin?

On Sat, Jan 11, 2025 at 9:43 AM, ok1mlg via

<ok1mlg=[email protected]> wrote:

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

OK. Flexibility is a good thing but excessive flexibility is counterproductive. The average user isn't capable of foreseeing all the things they could break with various settings. I'm not talking about time format settings specifically here, but more generally about the ability to configure everything in the applications.

But you didn't answer my question. Why do you require a 24-hour format specifically in the ham application, when you use a 12-hour format for everything else? I'm not criticizing you; I'm just very curious because it could guide my future steps.

so 11. 1. 2025 v?18:48 odesílatel Kevin Loughin via <loughkb=[email protected]> napsal:

What I have learned in dealing with the larger audience, and also through my working career in computer support in large companies, is that everybody has their own preferences. There is no one "right" way to do anything with a few exceptions.?

You want all of your applications to behave the same with this regard.? Myself, I would like most of my other applications to operate on local 12 hour time. But my ham radio applications to operate on UTC time. I suspect, from my interactions with others, that this is perhaps the more common scenario.?

In either case, flexibility within the application merely broadens its appeal and increases its level of comfort across the broader audience. Giving the user the choice, improves the acceptance and appreciation of the program.?

That's my two cents worth.?

Kevin?

On Sat, Jan 11, 2025 at 9:43 AM, ok1mlg via

<ok1mlg=[email protected]> wrote:

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