rouggy
9f5c482667
JTDX polls get_ptt DURING transmit to confirm the rig is keyed (WSJT-X does not, which is why it worked and JTDX cut after ~2 s). We answered a blanket "0" (RX), so JTDX concluded PTT had failed and dropped the over. get_ptt now echoes the last PTT state commanded via set_ptt — always consistent with the client's own command. Trace showed T 1 → three t→"0" polls → T 0.