I had the same issue as you describe and recalled that I had not selected the "Allow TX Frequency changes while transmitting" setting on the Settings...General tab. Checking this setting solved the first problem highlighted in this thread.
regards, Brian VE3IBW On Sun, Dec 2, 2018 at 10:07 PM Paul Kube <paul.k...@gmail.com> wrote: > Me three :). > > Well described by Charlie and Jim. > > 73, Paul K6PO > > On Sun, Dec 2, 2018 at 4:48 PM Jim Shorney <jshor...@inebraska.com> wrote: > >> >> Thanks Charlie! Nice to know it isn't just me... :) >> >> 73 >> >> -Jim >> NU0C >> >> >> On Sun, 2 Dec 2018 21:20:39 -0000 >> char...@sucklingfamily.free-online.co.uk wrote: >> >> > Hi Jim >> > >> > Yes, we experienced the same behaviour where clicking an earlier message >> > when bailing on a QSO ended up splitting the TX and RX frequencies. >> > >> > We also found it labour intensive to have to select TX4 and enable TX >> > manually when the calling station sent R report again, clearly not >> having >> > received our initial RR73 message. On some occasions we needed to do >> this >> > several times during more difficult QSOs. >> > >> > 73 >> > >> > Charlie G3WDG >> > > >> > > I have noticed a specific scenario that has happened several times >> during >> > > the contest. This happens when I have called a CQing station two or >> three >> > > times with no reply and I bail and go call another. Then I see the >> first >> > > station replying to me with TX3 while I am calling the new one. So I >> bail >> > > on that call and try to go back to work the first station with a >> > > double-click on the message. This moves the RX back to the first >> station's >> > > frequency, but not the TX. It is acting like Hold TX is on, but it is >> not. >> > > I tried toggling Hold TX. and shift-doubleclick, but the TX refuses to >> > > move until I use one those "confusing" arrows. (j/k, I'm not >> confused - >> > > much). >> > > >> > > Maybe I'm just a bad op. I know we are supposed to offset our signals >> and >> > > call split, but that doesn't seem to be happening. At any rate, it >> seems >> > > like the TX should move in this scenario, otherwise I end up QRMing >> the >> > > second op until I remember where I am. >> > > >> > > While I am at it, it would be nice if, when calling running station, >> Tx4 >> > > could me made sticky until the final 73 is received. Leave TX disable >> > > alone, just let Tx4 stay selected in case it needs to be re-sent. One >> less >> > > thing to have to scramble for when things don't go as planned. >> > > >> > > Anyway, 70 contacts so far before I needed to take a break. >> > > >> > > 73 >> > > >> > > -Jim >> > > NU0C >> > > >> > > >> > > -- >> > > The universe we're in will reach absolute zero in three hours. Safe is >> > > relative. - Idris, "The Doctor's Wife" >> >> >> _______________________________________________ >> 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
