mirror of
https://git.vladimir.cc/vladimir/ewsdr.git
synced 2026-08-25 20:37:33 +00:00
c849058d360468bc41f7a6ca26ebab0de275986b
The DUP toggle wrote FDisplayDuplex directly, bypassing the controller's SetDuplex (which also sets KeepRXDuringTX live and fires rfDuplex). And MainForm had no rfDuplex render case, so QO-100 auto-enabling duplex (ActivateXvtr → SetDuplex) left the button unlit while FDisplayDuplex=True — pressing DUP then turned it OFF when the user expected ON. Single path now: ApplyDUP just calls SetDuplex; a new rfDuplex render case styles the button and (when transmitting) switches the display source. Both the button and QO-100 auto-enable go through it, so the button always reflects state and KeepRXDuringTX stays in sync. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Languages
Pascal
96.4%
Python
2.9%
Shell
0.6%