We need to add one statement here probably
void MainWindow::on_dxCallEntry_textChanged (QString const& call){ m_hisCall =
call; statusChanged(); statusUpdate ();}
Tovoid MainWindow::on_dxCallEntry_textChanged (QString const& call){ m_hisCall
= call; statusChanged(); statusUpdate (); set_dateTimeQSO(-1);}
On Friday, January 11, 2019, 12:47:53 PM CST, Don AA5AU
<aa...@bellsouth.net> wrote:
This happens to me all the time. When you stop using WSJT-X, then go back a
few hours later, many times it logs the next contact with a start time of when
you last made a contact a few hours earlier. The end time is correct. The QSOs
usually get flagged by eQSL as not being in the log. That's how I discovered it.
I'm using JTAlert and DXKeeper, but this has been an issue for quite some time.
I know to either restart WSJT-X after a pause, or look at the first contact I
log after a period of inactivity.
Seems to be an issue with WSJT-X. I thought it was a known issue.
Don AA5AU
On Friday, January 11, 2019, 10:43:53 AM CST, Al <k...@arrl.net> wrote:
(WSJT-X V2.0.0, W 10 )
This may have been reported before ??
I was on earlier today and made several 80 contacts ending at 1319.
I left the radio running and came back at ~16:17 and changed bands to 17m.
My first contact on 17m was at 16:19 but the logs recorded that contact time
at 13:21.
AL, K0VM
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
