CQRLOG - bugs

cqrlog 2.3.0-1 and stack trace in remote mode for wsjt.

Submitted by ik0dwj on

Hi Petr!
I state that i use debian "buster".
With the previous version 2.2.0-1 the remote mode for wsjt worked well with CQRLog. With the new version 2.3.0-1, when I register the QSO in FT8 a pop-up of CQRLog opens with the warning of an access violation and I have two options: "CANCEL" or "SAVE". if I click on "SAVE" I run the risk of corrupting my data, if I click on "CANCEL" CQRLog disappears and only WSJT-X (1.9.1) remains active, however the contact is registered on CQRLog, as well as automatically it is uploaded on CLUB LOG and HAMQTH.

Forums: 

Cursor bug in RST sent field

Submitted by dk7ob on

Hello,

I just installed cqrlog 2.2.0(001) on a fresh Kubuntu 18.04 and notice a small cursor bug which I didn't see on my old 16.04 install:

If I use the TAB key to go to the "RST sent" field in CW mode, cqrlog fills in a 599 with the S field highlighted. That's fine. But if I enter an S value, say "5", it updates the "T" field, so the report becomes 595 instead of the expected 559.

Anybody noticed this bug too?

Regards,
Wolf, DK7OB

Forums: 

Unstable TRX control

Submitted by kb1fv on

I have seen several reports here of instability, mainly with Yaesu rigs. My problem is with Kenwood but the symptoms are nearly identical. Let me also state right here that FLDIGI operates flawlessly with my rigs. I have

* TS-140S with IF-10C and IF-232C
* TS-440SAT with IC-10 and IF-232C
* Computer is i5 with 8GB RAM
* OS is Xubuntu 16.04.03LTS
* CQRLOG version 2.2.0 (001)
* Hamlib v3.1

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs