That sounds reasonable to me....when doing this I just put it in for 
double-clicking on either window.  But the right side shouldn't need it.
Go ahead and remove the "set_dateTimeQSO(-1)" line from this section of code in 
mainwindows.cpp and see if behaves for you.


void MainWindow::doubleClickOnCall2(bool shift, bool ctrl){  
set_dateTimeQSO(-1); // reset our QSO start time  m_decodedText2=true;  
doubleClickOnCall(shift,ctrl);  m_decodedText2=false;}
de Mike W9MDB      From: Neil Zampella <[email protected]>
 To: [email protected] 
 Sent: Tuesday, July 4, 2017 12:03 PM
 Subject: Re: [wsjt-devel] Question about QSO Start & End Times
   
 UM .. how else do you respond when using JT65/JT9 .. I don't use the buttons 
on TAB 2.  Double clicking on a response in the RX window when I'm calling CQ I 
agree with, that should start the QSO, but double clicking in the TX window 
should not as its a  normal way to trigger the next dialog is a normal way to 
progress through the QSO.     
 
 Or am I missing something here?
 
 Neil, KN3ILZ
  
 On 7/4/2017 11:38 AM, Black Michael wrote:
  
  When you say "double click" you are talking about the double-clicking the 
message in the RX Frequency window?  That will reset the start time as of right 
now.
  
  de Mike W9MDB 
        From: Neil Zampella <[email protected]>
 To: [email protected] 
 Sent: Monday, July 3, 2017 6:44 PM
 Subject: Re: [wsjt-devel] Question about QSO Start & End Times
  
   In reply to your other post .. yes, I'm using JTSDK.
 
 Again, I'm using Tab 2, not Tab 1.  JT65/JT9 .. no auto sequencing.    Just 
double clicking to trigger the next response in the sequence.   
  
  On 7/3/2017 12:58 PM, Black Michael wrote:
  
  Any double-clicks on lines will reset the start time to "unknown". 
  When the QSO transitions to TX 2 or TX 3 the start time gets set.   Any 
double clicks on lines after that would also reset the start time.  Tx 6 also 
resets start time. If start time is not set by TX 2 or TX 3 then it will end up 
being the stop time. 
  And does autoseq sequence to "TX 6" by itself?  That would explain why 
autoseq modes get their time reset. 
  Mike 
 
            
    
      
 
 ------------------------------------------------------------------------------
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