On 07/02/2017 16:40, ANDY DURBIN wrote:
"what could that reasonable test be?"
It could be a test that the time span between the derived QSO start
time and the derived QSO end time did not exceed a user specified
maximum QSO duration. I would set it to 30 minutes. You could set
it to whatever time was appropriate for your fishing technique.
If time span is greater that user specified time then alert on log
attempt and allow acceptance or edit.
Hi Andy,
your test requires configuration, my proposal simply needs a manual
correction to the start time, in the very few cases that it is
potentially wrong i.e. long calls to break a pileup extending past QSO
matching service constraints. The facility to correct both start and end
time is already there. Why add more complexity -- I think less is what
is required here.
With my proposal I can definitively say the QSO start time you are
offered when you log was the time of your first transmission in a QSO
that referenced your QSO partners callsign -- no ifs, no buts, no
settings, no special treatment of different messages, no funky guesswork
and automatic adjustments. The only assumption is that standard messages
are used for the first QSO transmission, not a bad thing IMHO.
I wonder if too much effort is being made to try and make the start time
of both QSO partners match, that is not necessary nor required.
Added to all this you have the ALL.TXT file for reference so if in the
rare event you forget that the start time is too early due to an
extended call that is not heard and, say, if an LotW confirmation is not
forthcoming; you can review the QSO, adjust your log and re-submit the
QSO to LotW. Even easier if you use eQSL as you can simply adjust your
start time to that your QSO partner logged and uploaded -- but that is
another matter rendering eQSL somewhat pointless ;)
73
Bill
G4WJS.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
