feature: a. CQ call includes slot but you stay and listen on QRG
b. Once someone connects THEN you both QSY (auto prompts, suppress data till QSY'ed)
why: a. I don't have CAT set up so i have to manually QSY
b. i don't want to miss anyone elses CQ call while im hopped over to my listening slot
c. if im trying to connect to a few minutes old CQ call they may have moved back to QRG
This would marginally increase congestion on QRG but i think if you make it a selection you have to pick every time you call CQ it would keep its use reserved for when activity is low and you dont want to miss any calls.
I have considered this when developing the feature.
The one BIG flaw with this approach that made me put aside this concept is that there is no single moment where both sides knows for sure that they are connected. Here is an examples :
A send connect request to B
B respond ACK and thinks its now connected. But A did not receive the ACK.
B QSY to SLOT while A keep trying to connect on the QRG.
The other problem with this concept that you call CQ an hours ago on slot 1.
now someone respond and you QSY but the SLOT is already taken.
For that reason the only way to assure that the SLOT is free and both are QSYED to it is the way it is implemented now.
I hope it clarifies.