On 27/09/2017 13:47, Joe Taylor wrote:
Experimental new behavior for "Lock Tx=Rx" and for clicking on waterfall and decoded text.

Hi Joe,

I am failing to see why most of the existing automatic behaviour when double-clicking decodes has to be given up just for a number of operators who think that by default one's Tx offset should not be moved when replying to a CQ or QRZ call. To be clear, I agree that a simple means of calling a station without moving one's Tx frequency to them is necessary and there have been enough requests for a less onerous mechanism than having to ALT+double-click CQ calls to justify a different mechanism. As far as I can see the simple addition of a "Lock Tx Freq" check box on the main window achieves the necessary behaviour for those in the camp that wish to stay on a single frequency and not checking it should suit all those that want to follow "normal" radio communications practice. By normal communications practice I mean, you tune to find stations to call, you stay on a fixed frequency if you are the initial caller (CQ) and only adjust your Rx frequency (RIT) to track moving QSO partners. The new settings option does not revert to "normal" communications practice but  to a different model altogether.

I understand that there will always be a group of users who insist that the old "Lock Tx=Rx" option is needed but that option defintely causes poor operating practice that can cause QRM to other stations and I am glad to see that gone. The problem is that the new behaviour with "Settings->General->Double-click on call sets Tx and Rx freqs" is essentially equivalent to "Lock Tx=Rx", i.e. your Tx frequency is controlled by your QSO partner rather than yourself.

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

Reply via email to