I can see several possible solutions.
#1 After RRR log box pops up and disables Enable just one time.  If you Enable 
again it does not disable it again.  Should clicking the Log button then 
disable or just leave it alone?  Or, should Enable not be touched at 
all...period?#2 Option for RRR Log popup.#3 Skip the RRR log box popup for 
specific modes.  It's pretty rare on HF JT modes to have to repeat RRR...but 
MSK and such may want it a different way if RRR repeats are more frequent.
Give this patch a try and see how it works for you.  This should turn off 
Enable when the Log dialog pops up...but only one time.  If you Enable again 
and leave the log dialog up it should not disable again.  Does committing the 
log then disable it again?
Index: 
mainwindow.cpp===================================================================---
 mainwindow.cpp      (revision 7436)+++ mainwindow.cpp      (working copy)@@ 
-2942,7 +2942,7 @@     icw[0] = 0;     auto msg_parts = m_currentMessage.split 
(' ', QString::SkipEmptyParts);     auto is_73 = message_is_73 
(m_currentMessageType, msg_parts);-    m_sentFirst73 = is_73+    m_sentFirst73 
= is_73 && !m_logDlg->isVisible()       && !message_is_73 (m_lastMessageType, 
m_lastMessageSent.split (' ', QString::SkipEmptyParts));     if (m_sentFirst73) 
{       m_qsoStop=t2; 
de Mike W9MDB      From: Jay Hainline <[email protected]>
 To: 'WSJT software development' <[email protected]> 
 Sent: Sunday, January 1, 2017 9:26 AM
 Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent
   
#yiv3399694885 #yiv3399694885 -- _filtered #yiv3399694885 
{font-family:Helvetica;panose-1:2 11 6 4 2 2 2 2 2 4;} _filtered #yiv3399694885 
{panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv3399694885 
{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;}#yiv3399694885 
#yiv3399694885 p.yiv3399694885MsoNormal, #yiv3399694885 
li.yiv3399694885MsoNormal, #yiv3399694885 div.yiv3399694885MsoNormal 
{margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv3399694885 a:link, 
#yiv3399694885 span.yiv3399694885MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv3399694885 a:visited, #yiv3399694885 
span.yiv3399694885MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv3399694885 
p.yiv3399694885msonormal0, #yiv3399694885 li.yiv3399694885msonormal0, 
#yiv3399694885 div.yiv3399694885msonormal0 
{margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv3399694885 
span.yiv3399694885apple-converted-space {}#yiv3399694885 
span.yiv3399694885EmailStyle19 {color:windowtext;}#yiv3399694885 
.yiv3399694885MsoChpDefault {font-size:10.0pt;} _filtered #yiv3399694885 
{margin:1.0in 1.0in 1.0in 1.0in;}#yiv3399694885 div.yiv3399694885WordSection1 
{}#yiv3399694885 That’s not happening here Steve. If I CALL CQ and someone 
responds back with TX1, auto sequence then sends TX2. My QSO partner then 
responds with TX3. As soon as I receive that, autosequence sends TX4 and I get 
the prompt to log. Enable TX then goes back to gray and autosequence stops. I 
have to click on Enable TX to send TX4 again if I don’t receive anything.  I am 
also using r7436 working 6 meter msk144 mode.  Jay KA9CFD  From: Steven Franke 
[mailto:[email protected]] 
Sent: January 1, 2017 14:59
To: Joe Taylor <[email protected]>
Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent  
Autosequencing works fine here r7436, even after the logging box has 
appeared.Steve k9an 
On Jan 1, 2017, at 2:49 PM, Jay Hainline <[email protected]> wrote:  Yes it 
also stops the auto sequencing. I have to keep clicking on Enable TX to keep 
sending RRR. 73 Jay KA9CFD From: Black Michael [mailto:[email protected]
Sent: January 1, 2017 14:47
To: WSJT software development <[email protected]>
Subject: Re: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent The 
idea is that you don't click OK until you're happy with the QSO...but you've 
got the logging box there to remind you to do it.  I think some operating 
habits are hard to change.   Maybe it should be an option.  But is there a 
reason you can't just let the dialog box sit there until you're ready to log 
it?  It doesn't interrupt operations at all, does it? de Mike W9MDB From: Jay 
Hainline <[email protected]>
To: [email protected] 
Sent: Sunday, January 1, 2017 8:38 AM
Subject: [wsjt-devel] Prompt to log QSO when either RRR or 73 is sent This was 
introduced in r7431. I think its bad form to get a prompt to log the QSO when 
you are sending RRR. How do you know if your QSO partner has received it if he 
does not send 73 back to you?? Jay Hainline KA9CFDColchester, IL  EN40om 
------------------------------------------------------------------------------
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
  
------------------------------------------------------------------------------
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

Reply via email to