I'm loving VARAC version 3.4... with one exception, the QSY pop-up!
Actually, I like the QSY feature very much, but the pop-up appears with Yes already highlighted and ready for input. The problem is that if I'm typing something into the outgoing message buffer when the pop-up appears, the dialog box takes my typing as its input. The dialog box can then disappear and I won't know what it did and it may have done something I didn't want to do - like QSY down directly onto another nearby station instead of allowing me to not QSY down, but QSY Up instead.
I think it would be better if the dialog box for confirming a QSY request were somehow inactive so that the user would have to actively click on it to accept or deny the request. That way the user could continue typing his/her current outgoing message, send it, and then QSY.
Anyone agree? Disagree?
QSY windows has to steal the focus from the VarAC windows othwise it will remain behind it and may not be seen and you miss your opportunity to QSY.
the default is YES as in 99% you would QSY.
You also get a DING sound letting you know something happened.
I understand what you experienced but it is just a matter of practice and getting used to how it works.
I did get some request for a different sound alert to distinguish the QSY alert from others. I will include this.
I understand.
The only issue is that it steals focus while I'm typing and reacts to my typing. I want to QSY, but don't see the window because while I'm typing the words "Good to hear from you" into the buffer, the "Y" initiates the QSY. Or, if I'm typing "That's nice", the "N" cancels the QSY. Both of us want to QSY, but the other person initiated it without waiting for some idle time between exchanges.
Maybe the window can pop-up, but with neither YES or NO set as the default? This would require clicking on the dialog window and every time the user pressed a key, Windows would beep, indicating that some action was required (the default Windows operation when you press a key that's not expected in a dialog window).
Which bring up another issue. Sometimes QSYU/QSYD fails if one or other person is actively sending a message. I've had several QSOs where my message is being sent, the other person clicks QSYU/QSYD, and I get the pop-up, hit YES, and then we end up with one of us changing frequency, but not the other person. We end up chasing each other up/down the band as we QSYU or QSYD trying to find each other again!
As for not setting a deault button - Agree. I'll do it. I understand the case.
As for QSY - the moment you get the popup, the other side get the popup. with or without additional message in the QUEUE. the QSY popup only shows once the entire packet with the QSY incitation is sent (and received). What you are experiencing is a situation where some users (mostly new ones) need some time to read the popup message. they are overwhelmed and it takes some time (and practice) for them to get used to this.
We teach the ham radio world a new technique that was never implemented before so it takes time and patient.
I do plan to add 2 layers QSY system - one side invite. the other side need to approve. once the approve message is received on the QSY initiator, both sides will get the QSY POPUP. that would make things easier as both sides know they are fully aware of the process now.
Hello Irad and companions.
Thank you very much for your effort. The program is beautiful and fun.
I have done tests with a good friend here in Barcelona.
One detail that they tell me: When QSY is done, the cursor doesn't stay in the "New Message" window. That can cause some confusion. Otherwise great.
73
@Agustín Franco thanks for the kind words and bringing this focus issue up. I'll take care of it in V3.5
QSY popup and the timer 'countdown' is really annoying. If I have established a contact (example on 7105) There is usually enough time for a quick QSO and then RELEASE the frequency to someone else. That kinda works but is really no different than WSJT's canned messages..
What would be a better arrangement is for VARAC to suggest more than one frequency for users to select and then the user can then choose one and just call CQ (just like an SSB or CW QSO) that way several people are not listening on one Freq.
The calling freq can still the be used to 'beacon' a station or call CQ but include the other frequency - kinda like we do when using SPLIT on Contest (but in digi) - I hope I explained it well?
Any thoughts? as I hear a lot of dead-air?
The QSY countdown is annoying... yes :) what's more annoying is people conducting long QSOs on the calling freq. when trying to balance between the two - we prefer the first annoy type :)
As for expending - we have some plans for creating a new CQ method that will provide better scale as the mode becomes more popular.
@irad d
Well, irad, you have certainly stopped long QSO's on the frequency - be interesting to see how CQing develops! ;)
Honestly, I have so many more important things to ignore in daily life that the QSY message is a lightweight concern. I don't even see it. I throughly enjoy VarAC.
Trying to manage other's behavior or use is an uphill frustration and slippery slope at the same time.
:)