From hamlib freq readout, allow the QSO window to clear all data whenever band or few Kc change. (Like Logger32 does).
(I press enter if I make the contact, I move the VFO searching for another DX if I don't).
This saves the time to focus mouse and press Esc twice to clear the failed contact.
If found convenient and feasible, make it selectable on Preferences.
Thank you!
Hello,
this is very interesting idea. How many kHz? I just put it into my todo list. Thank you!
73 Petr
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Default to +/- 1 KHz.
User selectable frequency threshold if possible. (+/- 0.1-3KHz?)
Thank you Petr!.
This would be a great option!!
Tom K8WDX
Since the frequency readout changes to, let's say, VFO B while transmitting this would cause unwanted behaviour when working split.
Some major DX-peditions use receivewindows as large as 25 Khz. So my guess is that the VFO move would have to be selectable to at least some 30 Khz.
73, Tjalling PA3GOS.
Interesting, I think though that CQRlog only sees the A VFO, so not sure if this would be a problem, would be something to test when this comes out though..
Tom K8WDX
Well, I have "tested" it. And the readout changes to VFO B as soon as I transmit.
Not sure if hamlib/CQRLog can distinguish which VFO is used. If so, maybe this feature could be combined with automatic split when reported in the cluster.
73, Tjalling PA3GOS
Great idea - I like this clear Call too (it is superb using N1MM as contest program) and it can be about 500hz for CW or maybe set as variable.