Agreed, completely.  My use of the word “knob” tends to be generic, influenced 
by 40 years of high-end software development.  An operational parameter, 
controlled by some UI gadget.



Thinking about this over lunch, if I were implementing it, I would tend towards 
a delta-t adjustment that was reset to zero each time the program transitioned 
from “In QSO” to “Not in QSO”.  I would not automatically set the delta-t when 
going “into QSO”, but would leave that as a manual option once the QSO was 
being attempted.  That would encourage correct operation (getting the time 
right), but would still allow one to make the QSO with the DX station when they 
can’t (or won’t) get the time right.



It’s a small thing – but Mellish Reef on 160 !!!!



Dave / NX6D





________________________________
From: David Tiller <dtil...@captechconsulting.com>
Sent: Sunday, November 12, 2017 2:03:08 PM
To: WSJT software development
Subject: Re: [wsjt-devel] DXPedition System Clock Sync

David wrote:

"A knob could adjust WSJT-X’s notion of the time of day to “zero beat” the DX 
station, both in RX and TX so you can communicate, regardless of how far off 
the DX station’s clock may be."

There's no need for anything as programmatically complex or real estate hogging 
as a knob - a simple checkbox either on the config page (to set the time track 
option for all stations attempted) or next to the call sign box (to enable time 
track for the current station only) would enable the program to use the DX 
station's delta-T as your adjusted time value.

Again, all of these solutions presuppose that an internal delta-T value is used 
for framing timing as opposed to the actual wall clock time.

> On Nov 12, 2017, at 16:17, David Fisher <dsfis...@outlook.com> wrote:
>
> As I see it WSJT-X could do the same.  A knob could adjust WSJT-X’s notion of 
> the time of day to “zero beat” the DX station, both in RX and TX so you can 
> communicate, regardless of how far off the DX station’s clock may be.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! 
https://eur01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fsdm.link%2Fslashdot&data=02%7C01%7Ckq5stom%40outlook.com%7Cbf0fc91e72e149193aed08d52a1962b8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636461210874572111&sdata=%2B02TLAwB9s6iqMtirgmFsJdPuPVuSgwMTB251t2vHhM%3D&reserved=0
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fwsjt-devel&data=02%7C01%7Ckq5stom%40outlook.com%7Cbf0fc91e72e149193aed08d52a1962b8%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636461210874572111&sdata=Xmu0FcDbjOH8%2FWeQRl41L%2BhyVr%2B5QMutfpcQaG1vPn0%3D&reserved=0
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to