I have to agree that I like the new way of operating with rc3 rather than the old.
I have had many start up CQing on my frequency because the software caused them to do so. They work me, then they figure they would start CQing because hey, there's DX on the band. Right on top of me because both RX and TX moved. With this NEW behavior you basically have your own TX slot. Everyone should be monitoring the entire band and then the software picks up when someone calls you. One handed operation can be accomplished by clicking where you want to go, then click TX-> RX. Not super complicated... 73 Ria, N2RJ On Wed, Oct 18, 2017 at 3:27 PM, Bill Somerville <g4...@classdesign.com> wrote: > On 18/10/2017 16:23, Gary McDuffie wrote: >> >> If everyone were to split, only half the number of stations would fit in a >> given bandwidth. > > > Hi Gary, > > that is incorrect. Given N slots there are N possible QSOs, there is no > reason for any QSO to have both partners on the same frequency. Having both > parties to a QSO on the same frequency is conceptually simpler but in theory > one party may have QRM from half of another QSO or local QRN, in that case > moving improves the number of successful QSOs overall. > > 73 > Bill > G4WJS. > > > > ------------------------------------------------------------------------------ > 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 > wsjt-devel@lists.sourceforge.net > 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 wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
