Mike --
Thanks for submitting this patch. The plan now is to release v1.7.0-rc3
very soon, maybe this weekend. A GA release of v1.7.0 may follow within
about a week. When that happens, the development branch will become the
"v1.8.0" branch.
Because your proposed changes are rather extensive, I think we should
wait and put them into v1.8.0. Then we'll have plenty of time for any
necessary shakedown.
-- Joe, K1JT
On 12/2/2016 3:54 PM, Black Michael wrote:
> This is a further improvement on the QSO Time On/Off patch.
>
> https://www.dropbox.com/s/ds88fzk3r0hz3s1/datetimeqso.patch?dl=1
>
>
> TimeOn has been added to the UDP log message and Time renamed to TimeOff
> (which is what it was representing before).
> Log window has both TimeOn and TimeOff now so users can explicitly set
> the values if needed/desired
> wsjtx.log changed to ISO date standard and added TimeOff
> Updated UDPExamples
>
> Tx 2/3 is used to set TimeOn -- this overcomes the problem of sitting on
> Tx 1 and then waiting for an opening to start the QSO causing the log
> time to be too early.
> TimeOn is backed up by the appropriate 1 or 2 transmit period cycles
> respectively and should work in all modes and future modes.
>
> MM1PTT is in this thread showing how he had many missed QSLs due to
> inaccurate logging info. A good example of why we need some improvement
> in this arena.
> https://au.groups.yahoo.com/neo/groups/HamApps/conversations/topics/12908;_ylc=X3oDMTM3NjJmc3RqBF9TAzk3NDkwNDMzBGdycElkAzc0OTAyMDE3BGdycHNwSWQDMTc0MDA2MzEwOARtc2dJZAMxMjkyMQRzZWMDZnRyBHNsawN2dHBjBHN0aW1lAzE0ODA2NjgzODcEdHBjSWQDMTI5MDg-
>
> This patch should overcome these problems and allow accurate logging via
> external applications like JTAlert and others without trying to guess
> the start time via other means.
> This patch makes a pretty accurate start/stop time for QSOs.
>
> It covers the following situations:
> #1 Standard QSO
> #2 Double-clicking a CQ, disabling transmit, wait for other QSO to
> finish, and Enable again..QSO startime will relative to Enabled again
> #3 Double-clicking a CQ and just hanging on waiting for an answer...QSO
> start time will be 2 transmit periods prior to Tx 3 (or R+dB on tab 2)
>
>
> Please give this some consideration....
>
> de Mike W9MDB
>
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
