Not sure if this is a bug report or a feature request...
When involved in a QSO, it's possible for one station to send a QSYU/QSYD command, while the other person sends an identical (or opposite) QSY command almost simultaneously. Both stations are prompted to QSY with a pop-up dialog box. One station hits yes , thinking he's confirming his own QSY, and a QSY is performed at that station. However, he was really confirming the QSY request from the other station! He then gets the the prompt for his own QSY request, and maybe it takes its input from the characters he's typing into the New Message box and it does ANOTHER QSY! Now he has moved twice and the person he is communicating with is left one QSY behind. The two stations will not link up again as they are transmitting 750Hz apart. The problem can also happen when one station sends a QSYU and the other station sends a QSYD. If the pop-up dialog box is cleared due to the operator typing a message and hitting enter (to send his message --- but the dialog box takes that Enter key as a "Yes, go ahead and QSY") then then the stations could end up 1500Hz away from each other. The operator typing may not even see the dialog box because it shows up just as he's hitting Enter to send his message.
Maybe this could be avoided by having a QSY timer. For example if either station receives a QSY request within 30 seconds of a previous request, that request is either ignored (not great) or there's a pop-up which says it could be a duplicate request. There should be no keyboard shortcut or default action on this window, otherwise regular typing could be taken as the response and the problem continues. This would force the user to read the prompt and manually click on it.
Released in V3.7.9