Re: [wsjt-devel] Pulled back on 73

2017-08-05 Thread Mark Turner via wsjt-devel
Hi Jim, I concur re habitually unchecking "Lock Tx=Rx" when sending Tx6 ("CQ") - I curse myself when I've forgotten to do it and someone calls me split, consequently finding myself dragged off to their qrg. Calling cq and then accidentally leaving the original qrg seems to be considerably more

Re: [wsjt-devel] Pulled back on 73

2017-08-04 Thread Pedro Carlos Pocciotti
Dear James, Do not forget to set as "*checked"** the box on "TX after sending 73" on Settings-Behavior configuration General Tab.* 73's Pedro - PY2HH Sent with Mailtrack

Re: [wsjt-devel] Pulled back on 73

2017-08-04 Thread James Shaver (N2ADV)
Thanks, Bill! I typically keep the box unchecked myself when calling CQ but I know there are folks who find it handy. Appreciate the peek! Jim S. N2ADV > On Aug 3, 2017, at 9:32 PM, Bill Somerville wrote: > >> On 04/08/2017 02:22, James Shaver (N2ADV) wrote: >> I had a FT8 QSO with W7PSK e

Re: [wsjt-devel] Pulled back on 73

2017-08-03 Thread Bill Somerville
On 04/08/2017 02:22, James Shaver (N2ADV) wrote: I had a FT8 QSO with W7PSK earlier (thanks!) where I was calling CQ, he responded to me, we went through the sequence, he sent his 73 and then moved off to call CQ elsewhere on the band. Unfortunately, my 73 pulled his TX back to where I was caus

[wsjt-devel] Pulled back on 73

2017-08-03 Thread James Shaver (N2ADV)
I had a FT8 QSO with W7PSK earlier (thanks!) where I was calling CQ, he responded to me, we went through the sequence, he sent his 73 and then moved off to call CQ elsewhere on the band. Unfortunately, my 73 pulled his TX back to where I was causing him to accidentally start calling CQ where he