Linux Mint 22.
CQRLog: version alpha_(130)_Gtk2
WSJT-X: version 2.7.0-rc3
In previous versions (2.6.0_001) of CQRLog and WSJT-X, and while CQRLog was running in "Remote mode for wsjt CTRL+J" anytime new callsigns were decoded in WSJT-X running ft-8 mode, the "Call" field in CQRLog would remain empty, until I specifically double clicked on a callsign to work in WSJT-X. Then the "Call" field in CQRLog would populate and everything worked as expected.
Since I installed CQRLog alpha_(130)_Gtk2 and while I also have WSJT-X running, now every time a callsign is decoded in WSJT-X, CQRLog automatically fills the "Call" window... Without my interaction. It does it on it's own. This is improper behavior that I believe is a bug in CQRLog. I am still able to double click on stations to work in WSJT-X and CQRLog works properly, but the "Call" field window in CQRLog should NOT automatically get populated.
Thanks,
Bob, WG9L
Hi Bob!
That is not bug it is a property of CqrlogAlpha.
If you enter a callsign to wsjtx "DX call" field and have "wsjt remote" on it will appear to CQrlog/NewQso/call field. Same if you populate "DX call" by clicking decoded line (in wsjx window or Cqrlog/Cq-monitor/Map)
That is for you to see the information of the call from QRZ/HamQTH right away before even start of qso (same like you would do it manually when working CW or phone)
DO not worry the contents of New QSO. If you do not select that call, and enter another callsign to wsjtx "DX call" field, contents are cleared and new ones fetched.
If you work qso with wsjtx and press "OK" button in wsjtx/log_qso window those (final) values (report etc.) are saved for qso, via remote connection, with information from QRZ/HamQTH already in NewQSO.
Same, other way around, if you double click a Cqrlog/DXCluster/Spot having wsjt remote running the callsign from spot is added to NewQSO and also to Wsjt "DXCall" with rig changed to spot frequency.
--
Saku
OH1KH