CQRLOG - bugs

Import ADIF: QSO comments go in wrong field

Submitted by M0TRN on

Hi,

I'm just getting started using CQRLog (still using fldigi in parallel, as I haven't gotten used to it yet)..

One thing I noticed, (and there are more, will post more reports), when I imported my ADIF from fldigi, the comments for each QSO have been put in the "Comment to callsign" field instead of in the "Comment to QSO" field, this means that where there are more than 1 QSO they don't get saved and also that if I have a new QSO with someone the comments from the previous QSO gets overwritten.

Please fix it so it gets imported into the right field!

Forums: 

Club membership files must be installed to /usr/share/cqrlog/members (Debian package)

Submitted by N0NB on

Hi Petr and Martin.

I have discovered that CQRlog 1.2.1 in Debian Sid must have the club membership file--skcc.txt in my case--copied to the system directory of /usr/share/cqrlog/members for it to be loaded. I tried creating ~/.config/cqrlog/members as it did not exist and copying skcc.txt there. Looking at the club1 table showed that the newest members were not added. Once logged in as root I copied skcc.txt to /usr/share/cqrlog/members and the table was updated as expected.

I don't think this is a Debian packaging bug which is why I'm reporting it here.

Forums: 

Name not updated if callsign is edited

Submitted by la4vga on

If You enter a callsign and press TAB, the program will lookup name and QTH.
But if You edit the callsign (i.e one letter), and the press TAB, the name and QTH field is not updated.
You can see the callbook window updating

This has to be done by dobble-ESC, and the enter correct call.

73 de Børge / LA4VGA

Forums: 

Switching databases leaves QTH profile at previous DB

Submitted by N0NB on

I hate to add to your already long TODO list. ;-) I have several databases, each for a specific callsign I've used and am using QTH profiles to manage my operating locations. So far, so good.

I have found that when I open CQRlog anew and select a DB, work in it a while, and then select 'File|Open or Create New Log' that after opening the second DB (or any subsequent DB) the profiles remain from the first DB open. Closing CQRlog and then selecting the desired DB at the program's start results in the proper QTH profiles being available.

Forums: 

ADIF import -- Region 2 2m frequency rejected

Submitted by N0NB on

I'm importing the logs from the 0.9.x installations (yeah, I'm late) into 1.2.1 on Debian Sid. In one log I have four frequency errors I cannot resolve. I noticed that all four of the frequencies are in the upper part of the 2m band which is legal here in the USA. I went into the preferences adjusted the band limits for Region 2, USA. I tried the import of the four errors (after edting out the ERROR: lines) and received rejection of all four records.

Forums: 

Not all QSO's exported for QSL label printing

Submitted by do4nw on

Since CQRLOG 1.x, only the first few hundred QSO's or so are shown in the QSO list instead of all QSO's. Is there a way to show all QSO's again?

It's troublesome because of this issue: When i click on "Export for label printing", only those QSO's that can be seen in the QSO list are exported, but not the complete logbook.

Forums: 

TX Control sometimes does not work

Submitted by do4nw on

Every third program start or so the TRX control shows the frequency 0.0000 and CAT does not seem to work.

I'm using Ubuntu 10.04 with a Yaesu FT-847 and CQRLOG 1.2.1.

Here is the console output when TRX does not work:

test@shack:~$ cqrlog
Loading libssl: /usr/lib64/libssl.so
Loading libcrypto: /usr/lib64/libcrypto.so.0.9.8
Loading libmysqlclient: /usr/lib64/libmysqlclient.so.16
*
User home directory: /home/test/
Program home directory: /home/test/.config/cqrlog/
Data directory: /home/test/.config/cqrlog/database/

Forums: 

dxclusters table corrupted

Submitted by AB1KW on

For unknown reasons, sometimes cqrlog corrupts the dxclusters table. After that happens, clicking the "Select" button in the dx cluster window results in a "Operation cannot be performed on an inactive dataset." pop-up, asking me to either kill cqrlog or risk data corruption.

Other windows still work fine, for example the QSO list.

Running myisamchk -r on the dxclusters table (after quitting cqrlog!) does not seem to fix the issue...

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs