Bill, Re: Multiple decodes on strong signals. Thanks very much for your insight. Those of us in the local club who have observed this can throw a scope on my line and see if it is in my system. The multiple decodes have been predominantly from US stations, most of them 1000 miles or more from me. I've had some instances from the Caribbean but no one from the UK so you boys are off the hook, hi. (Northern latitude stations are not very strong here in FL.) I can reduce my filter bandwidth easily so I will give that a try to see what happens with the extra decodes.
Re: Resetting the Colors "Stick" is not a good choice of words I'm afraid. What I meant was, when I had to restart the program after taking a break, I had to go in and check "reset highlighting" to get it to populate and display the colors. Re: Re-syncing RX and TX Windows Yes, holding the TX frequency and alternating between run and S&P is a great feature. My thought was for the program to re-sync the RX window to the TX window automatically after I completed a QSO with a calling station while I'm running. Doing the same thing applies if I go S&P while staying on my TX frequency. This may all be moot if I am bouncing back and forth from run to S&P since I have to click on the station calling me anyway. On Mon, Dec 3, 2018 at 9:51 PM Bill Somerville <g4...@classdesign.com> wrote: > On 03/12/2018 20:25, Ed Deichler wrote: > > When running on a frequency and the program auto-shifts to the calling > > station's frequency, and I had to manually move it to the TX frequency > > after I sent the “73” message. Perhaps a better way would be for the > > RX window to shift automatically to wherever the station is calling > > (including my transmit frequency) so that manual re-syncing to the TX > > window is not necessary. > > Hi Ed, > > if I understand your comments above correctly then the "Hold Tx Freq" > check box is probably the best option all around. With this checked you > can find a clear slot to Tx on and stick with it for both run and s&p > mode, or at least until it becomes unproductive from QRM. > > 73 > Bill > G4WJS. > > > > _______________________________________________ > 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
