Holding a long conversation on a watering hole frequencies (14.105, etc) prevents other users on that special frequency. Perhaps setting a timer (5 minutes) at the start of the conversation and popping dialog with the timer expires suggesting to change frequency +/- .750 MHz (per Gary's Nov 12th request).
I'm not sure automatic QSY is a good thing, though.
Reasons not to have automatic QSY
both parties should agree before changing frequencies
US parties might need to CW id before changing frequencies
don't want to QSY back onto the "watering hole" frequency
rig control (OmniRig) doesn't work for me yet
@rtykulsker
Feature request status: APPROVED
Feature development: DONE
Future release version : V2.7
Comments: No popup will be introduced as it is hard to track if people already QSYed. But duration was added.
See screenshot
I'm running 2.6.2. I tried the QYSD gesture on a QSO this morning. A pop-up was "eventually" displayed. I assume that occurred after the request was delivered to the other party. My message said to change frequency quickly to avoid losing the connection. Well, I did QSY down and did lose the connection. Eventually we did connect up and resumed our conversation.
So, it worked, kinda!!!
I do think that a non-modal, non-blocking popup would be useful. On the receiving side, I think there should be two buttons: [Agree] and [Disagree]. If the receiver clicks on [Agree]:
1) transmit the [Agree] message back to the original requestor
2) use rig control to QSY up or down. If rig control not enabled, message the user to change frequency
3) close the popup
When the requester receives an [Agree] response,
1) use rig control, etc.
2) close the popup
If the recipient clicks on [Disagree]
1) send a message back to the requester
2) close the popup
When the requester receives a [Disagree] message
1) tell the user in the popup
2) close the popup
The popup should be non-modal so that both parties can continue to chat.
Perhaps allow the recipient to also send back an QSY amount other than .750
Cheers,
Bob
Released in 2.7.2. Moving thread to "Released"