Jim:
Today, I went back to my first saved FT8-RU test contest and the Contest
Log compared to my actual HRD LB spot on as did the one from this weekend.
As stated to Bill, my Windows 10 Pro clock is set to display 24hr
(HH:MM:SS) using Windows clock settings, and I use T-Clock to actually
display
I would also be interested to find our what is going on here. It seems like
there are in reality two issues? Every computer has the log displaying in 12
hour format, and some computers additionally displaying local time while others
(who live nowhere near the prime meridian) display correct UTC
Bill:
My computer is set for Central Time USA and not UTC. The Contest Log has
always shown the correct UTC since the first RU test.
On Mon, Dec 3, 2018 at 11:34 AM Bill Somerville
wrote:
> On 03/12/2018 17:18, WB5JJJ wrote:
>
> Explain me this. My UCT was correctly logged in the Contest Log
On 03/12/2018 17:18, WB5JJJ wrote:
Explain me this. My UCT was correctly logged in the Contest Log from
the get go. 24 hour and all. My Win10 system was already set for 24
hour display and I use a program called T-Clock to display the time in
the lower right Task Bar spot replacing the dinky
Bill:
Explain me this. My UCT was correctly logged in the Contest Log from the
get go. 24 hour and all. My Win10 system was already set for 24 hour
display and I use a program called T-Clock to display the time in the lower
right Task Bar spot replacing the dinky Windows clock and sync my time
On 03/12/2018 03:59, Rich Zwirko - K1HTV wrote:
I noticed during the FT8 RU that the log page, although in UTC, is not
in the 24 hour format but uses the 12 hour plus AM or PM. Who uses UTC
in 12 AM/PM format? Almost all Ham logs are in 24 hour format, right?
73,
Rich - K1HTV
Hi Rich,
alrea
I noticed during the FT8 RU that the log page, although in UTC, is not in
the 24 hour format but uses the 12 hour plus AM or PM. Who uses UTC in 12
AM/PM format? Almost all Ham logs are in 24 hour format, right?
73,
Rich - K1HTV
___
wsjt-devel mailing li
From: Pino Zollo
> To: wsjt-devel@lists.sourceforge.net
> Sent: Sunday, April 30, 2017 5:30 PM
> Subject: [wsjt-devel] UTC
>
> Suggestion:
>
> Print the times in the UTC column with a colon between hours and
> minutes. e.g.
>
> instead of 22
Why? Either way is ISO8601.
de Mike W9MDB
From: Pino Zollo
To: wsjt-devel@lists.sourceforge.net
Sent: Sunday, April 30, 2017 5:30 PM
Subject: [wsjt-devel] UTC
Suggestion:
Print the times in the UTC column with a colon between hours and
minutes. e.g.
instead of print 22:22
Suggestion:
Print the times in the UTC column with a colon between hours and
minutes. e.g.
instead of print 22:22
TU
de Pino ZP4KFX
--
Check out the vibrant tech community on one of the world's most
engaging tech
Hi Mike,
On 17/02/2017 16:22, Black Michael wrote:
Ahhh..so it was logging correctly but on a client receving the object
it would misinterpret.
*Should have misinterpreted!* I am a little surprised that no one
decoding the UDP messages has pointed out that they are flagged as local
time even t
ry 17, 2017 10:14 AM
Subject: Re: [wsjt-devel] UTC
On 17/02/2017 16:05, Black Michael wrote:
I see the patch set Qt::UTC.
I was getting UTC times on my system. Do you perhaps have an environment var
that changes the time zone that Qt is using? I can't find any reference on
e
On 17/02/2017 16:05, Black Michael wrote:
I see the patch set Qt::UTC.
I was getting UTC times on my system. Do you perhaps have an
environment var that changes the time zone that Qt is using?
I can't find any reference on environment variables overriding
defaults. I'm running on Windows 10.
Bill..I see the patch set Qt::UTC.
I was getting UTC times on my system. Do you perhaps have an environment var
that changes the time zone that Qt is using?I can't find any reference on
environment variables overriding defaults. I'm running on Windows 10.
And since you set UTC after the times h
14 matches
Mail list logo
