On 5/6/19 at 4:36 AM, g4...@classdesign.com (Bill Somerville) wrote:
Such a change is possible although quite complex given that
time is read in several places and it would be disruptive of an
already complex application to maintain a separate source of
time consistently. TBH we would prefer that users take the
relatively simple steps necessary to keep their PC time
synchronized to UTC, within a few milliseconds, automatically.
When the station with the clock in serious error is a rare DX, I
think what my son calls the "Wedding Time Rule" applies:
"The bride is always on time. When she arrives, set your watch
to the start time specified on the invitation."
(Note that rare DX stations may have more problems with accurate
time than people with good Internet connections.)
I had this problem with a DX station and never figured out how
to manually set the time on my MacOS system to fix it.
Fortunately, the DX corrected his clock and I managed to make a QSO.
I am very sympathetic with the structural problems in wsjt-x
that make a centralized source of time difficult. I have worked
on large software systems that "just grew" and fixing this kind
of issue can be an amazing time sink.
73 Bill AE6JV
-----------------------------------------------------------------------
Bill Frantz | gets() remains as a monument | Periwinkle
(408)356-8506 | to C's continuing support of | 16345
Englewood Ave
www.pwpconsult.com | buffer overruns. | Los Gatos,
CA 95032
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
