Time Display Trigger

[KD5SMF]

UCT Time format is, and always has been 24 hour format. Why then does the “triggers” time clock only display 00:00 to 12:00 when setting up for alerts?
The app properly displays it however, when setting up the time triggers it does not here on the web site. This is confusing especially when your trying to catch a special event station, or DX entity.

[HB9DQM]

@KD5SMF

The app properly displays it however, when setting up the time triggers it does not here on the web site.

That is because HTML time input fields depend on the system locale – on my systems set to use a 24 hour clock, it works properly. Guess I should replace them with plain text fields so they work the same regardless of how the user’s computer is configured.

I’ve created an issue on GitHub:

Replace HTML time input fields with plain text

See also:

Time inconsistencies

Tried to set up a certain time to monitor some specific calls or areas. It seemed to promote “AM” and “PM”, but yet specifies Zulu time. Only when I exited out did it show Zulu. Might it be better to keep Zulu consistent throughout as the AM/ PM is confusing and not correlating with Zulu anyway?

TIme and Day of the week filters

Hi. Time filter set form 2200 - 0700 (should ditch the AM / PM thing when setting the time and make it 24 hour for UTC) Day of the week set to Saturday and Sunday. What I’d like to know is - does the day of the week activate on the start of the filter time or the end of the filter time? Or will this get ugly crossing over 0000 UTC?

[OH2BUA]

Hi,

my system locale in Win11 is 24-hours time. All regional things are set to Finland / metric.

Win OS language is english, as well as my Firefox is in english.

I very rarely face that AM/PM-thing. In HamAlert, yes.

73, Jukka

[HB9DQM]

This has now been fixed.