Were you progressing by double-clicking the messages instead of using the
buttons?
Right now that resets the start time. Maybe that needs to be changed.
doubleClickOnCall2 and doubleClickOnCall both reset start time.I think the
set_dateTimeQSO(-1) could be removed from both of those.Do we have something to
detect that a message has a sig report in it? That could cover the
double-clicking situation.
Currently if all you do is double click on messages both times should end up
defaulting to the log time.
de Mike W9MDB
From: Bill Somerville <[email protected]>
To: [email protected]
Sent: Tuesday, February 7, 2017 10:21 AM
Subject: Re: [wsjt-devel] WSJT-X: QSO start and end times
On 07/02/2017 16:16, Bill Somerville wrote:
> 1534 Transmitting 14.076 MHz JT65: G4WJS G0FUN 73
> 1535 -1 0.1 1500 # G0FUN G4WJS 73
...
Sorry prematurely sent e-mail.
I believe Station A (G4WJS) had a log window showing time on and off as
15:31 and Station B (G0FUN) was offered time on and off as 15:34.
I have still not seen any response to my proposal of:
"Maybe something like:
The time of the first transmission of a standard message that is not CQ
or QRZ for a new DX call. DX call here being defined as the base call to
allow for the discovery of a compound call part way through a QSO."
that yet convinces me that it is not a better solution.
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
------------------------------------------------------------------------------
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
