When editing any field (Call, Name, QTH, Comments, etc.), after deleting a character, the cursor is moved to the end of the next character. Very difficult to make corrections with cursor moving to unexpected place during edits, especially managing DX pileup, etc.

Also, RST sent and rcvd fields are not being populated with default values set in preferences for New QSO anymore.

CQRlog version 2.0.2 (001) binary version
OS: Archlinux 64-bit

73 Eric NO3M

Hi all,

I post this in the "bugs" section, although I'm not sure this comes from CQR.

When I start CQR, all input fields are white.
If I open "preference", the other windows are greyed, because they lose focus.
But when I close "preference", the windows stay greyed, although CQR is still working correctly. I have access to all fields and functions... but everything stays greyed.
This does not appear when I navigate through other windows (ac cluster, or details, or QSO list.

Hi,

I am using FT-857D and control it with CQRlog.
I noticed that CQRlog changes step for FM. Default is 12.5, and it changes to 5khz.

Thomas

Hello,

New install of CQRLOG 2.0.1 into Ubuntu 16.04 64-bit from the PPA.

Here's the scenario. I start the program. Everything loads fine, including transceiver control. I go to Windows -> TRX control. The TRX control window loads. It also works. I close the TRX control window. CQRLOG's ability to talk to the radio ceases, because rigctld is no longer running.

To restore it, I go to File -> Refresh TRX/ROT control. This restores rigctld and all is well.

I do use "Run rigctld when program starts", if that is relevant.

- Jeff KG8IU

Hello,

I installed CQRLOG 2.0.1 fresh into Ubuntu 16.04 64-bit last night from the Launchpad PPA. I noticed that sometimes when I try to open the Preferences, it doesn't seem to do anything. When I try a second time, usually it opens, but occasionally the open CQRLOG windows fade grey -- Unity's way of telling me they've met an untimely end. I've been running the program with --debug=1 in the terminal and nothing appears when this happens. In fact, the debugging logging just stops.