I just confirmed this behavior. If you re-enable during the LogQSO popup it
gets turned of when you click OK.
de Mike W9MDB
On Tuesday, August 6, 2019, 09:40:29 AM CDT, Dave Slotter, W3DJS
<slotter+w3...@gmail.com> wrote:
No, it's not happening because of 73 messages. Please re-read what I wrote
before and it should become clear to you that it is happening due to the
Logging window code.
--Dave Slotter, W3DJS
On Tue, Aug 6, 2019 at 8:50 AM Matthew Miller <mmill...@mail.umw.edu> wrote:
Are you sure its when you hit OK and not the next 7.5 sec interval with the
other station still sending 73?
I have frequently had problems where the Enable button is shut iff repeatedly
because the station I just worked keeps sending the 73 message over and over
and every time it disables my TX button even though it seems to understand that
I already logged it the program doesn't understand it already disabled TX at
the end of a contact.
It happens in FT8 too but mire in FT4 where it seems the other station keeps
sending the last part repeatedly.
Sent from my Verizon LG Smartphone
------ Original message------From: Bill SomervilleDate: Sun, Aug 4, 2019 7:31
PMTo: wsjt-devel@lists.sourceforge.net;Cc: Subject:Re: [wsjt-devel] Patch
Submission: Log Window : MainWindow::aceptQSO()
Hi Dave,
thanks, that's much better.
I will have a look at why that does what you desire, at first glance it doesn't
seem correct but the "Enable Tx" should not be being disabled by any logging
activity so something is wrong somewhere.
Do you have "Settings->General->Disable Tx after sending 73" checked?
73
Bill
G4WJS.
On 05/08/2019 00:26, Dave Slotter, W3DJS wrote:
Bill,
Here you go:
--- mainwindow.cpp.orig 2019-08-04 17:05:04.498325760 -0400
+++ mainwindow.cpp 2019-08-04 17:11:08.925398800 -0400
@@ -5540,7 +5540,6 @@
}
if(m_config.clear_DX () and SpecOp::HOUND != m_config.special_op_id())
clearDX ();
- auto_tx_mode (false);
m_dateTimeQSOOn = QDateTime {};
auto special_op = m_config.special_op_id ();
if (SpecOp::NONE < special_op && special_op < SpecOp::FOX &&
73,
--Dave Slotter, W3DJS
On Sun, Aug 4, 2019 at 7:24 PM Bill Somerville <g4...@classdesign.com> wrote:
On 04/08/2019 23:00, Dave Slotter, W3DJS wrote:
Hi WSJT-X Devs,
I have encountered what is, to me, an annoying behavior of WSJT-X's log window
that impedes my ability to multitask.
When I'm in FT4 mode, with those 7.5 second cycles, every second counts to get
the next QSO, so once the Log Window pops up and the "Enable Tx" button is
disabled, before I do anything with the Log Window, I immediately click on the
"Enable Tx" button to re-enable it. Then I go fill in the empty fields of the
Log Window dialog and click OK. Unfortunately, clicking OK causes the "Enable
Tx" button to be disabled (a second time), thus forcing me to click the "Enable
Tx" button a second time.
And if I forget to click the "Enable Tx" button a second time, I may lose
precious cycles with my rig not transmitting new "CQ W3DJS EM83" messages.
So I dug into the source code, and in less than five minutes, found the line of
code in question, and I disabled it, and all is good for me now.
I would thus, like to submit my very first patch request for version 2.1.0 of
WSJT-X:
dave@Moonquake:~/projects/hamradio/wsjtx-2.1.0/src/wsjtx/widgets$ diff
mainwindow.cpp.orig mainwindow.cpp
5543d5542
< auto_tx_mode (false);
Apologies if this causes some unwanted behavior, but for me, this works great.
--Dave Slotter, W3DJS
Hi Dave,
thanks for your proposed change but a diff with no context is no use to us.
Please provide a unified diff format or at least something with some context
and line numbers.
73
Bill
G4WJS.
_______________________________________________
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
