On 26/01/2014 18:29, Bob McCormick W1QA wrote:
Hi Bob,
I have these options checked / enabled:
- Prompt me to log QSO
- Tx disabled after sending 73
Whilst in a JT9 QSO I was transmitting the R +dB sequence. At 35 seconds in
I clicked on the 73 button with the intention of preloading the next message
in the sequence. When the R +dB sequence completed transmission the Log QSO
window opened.
I waited for the RRR message to be received and then clicked OK in the Log
QSO window. That had the effect of toggling the Enable Tx function off. I
noticed that - and clicked Enable TX in time to get the 73 sequence
successfully sent.
And at the end of that sequence I got another Log QSO pop-up window.
It would seem that by my clicking on the 73 button I've set a state
somewhere that triggers the prompt for Log QSO no matter what the actual
transmission was. And with the other setting (to turn off transmit after
73) this logic results in two unexpected events.
Would it be possible to adjust the code such that the post 73 sequence logic
is only fired at the end of the real 73 sequence?
I suspect that what actually happened was that the message being sent
when you first clicked the "73" button changed from R+dB to the 73
message. Such changes of message are allowed during the TX period. The
rest of your description is consistent with that i.e. as far as the
program is concerned you changed your mind and switched to a 73 message
mid TX period. The shutdown of auto TX and the triggering of the log
window are following a valid 73 message being sent.
It is best to only select the next message after the TX of the previous
message (more normally after the QSO partners decode has completed),
there is no "TX message pre-loading" capability as you describe it.
Bob W1QA
73
Bill
G4WJS.
_______________________________________________
Wsjt-devel mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/wsjt-devel
