Hi,
I'd like to filter QSO's from worked DXCC, but never confirmed in LOTW...
Any idea how?
73, Tom

New problem, I am not able to set any preferances, when I open Preferances I get an Error message "TListBox Index -1 out of bounds 0....25 
Then the usual ok to ignor or cancel ti kill... 
any ideas?? Thanks Tom K8WDX

I would like to be able to right-click on a QSL manager in the QSO view/edit form and search them via HamQTH/QRZ directly.
 
Currently we can right click on the call worked, but if they have a manager listed in the database sometimes it is helpful to go straight to the manager's page.  The manager often lists requirements such as bureau/no-bureau, greenstamp requirements, etc.
 

I got this error when trying to remove dupes from the log:
 
ERROR: : Error executing query: Cannot truncate a table referenced in a foreign key constraint (`cqrlog001`.`log_changes`, CONSTRAINT `log_changes_ibfk_1` FOREIGN KEY (`id_cqrlog_main`) REFERENCES `cqrlog001`.`cqrlog_main` (`id_cqrlog_main`))
 
Dupes will not be removed.
The problem is the log from wsjt-x. wsjt-x is using his own Log "wsjt-x_log.adi" for checking for worked Callsigns and Countrys. So it's not a good idea to delete this log after using it for importing qso into cqrlog.

Petr,
Is it possible to have the frequency of the radio echoed to other devices?  I have a SteppIR antenna, an Acom2000A amplifier, and a Palstar AT-Auto which all would like to hear what frequency the radio is on.  However, CQRLOG will only talk to the radio and a rotator.  How difficult would it be to add and amp, tuner, antenna option so as to have CQRLOG echo the frequency to them?

KX3 native CW keying support via KY cat commands like in N1MM 
 
https://k4mtx.wordpress.com/2013/06/02/kx3-how-to-configure-n1mm-to-use-...
 
Taht functinality will be huge handicap for Elecraft users, and gives one cable less in hamshack :-)

V 1.8.2 (Fedora 20) when log is open and rigctld is working:

Change another existing log with "Open or create new log". When other log is up and running QRG will not
follow rig any more (or cqrlog will not drive qrg).

Rigctld is not dead it can be used from terminal window via telnet. Cqrlog does not get connect, not even when "Refresh TRX/ROT control" is used.
Only way to get QRG reading work again is restart whole program.

Hi Peter,
 
When you have set OFFLINE, and click on the clock next to the QSO-time, it will not insert the current time.
I use offline for non-connected tranceivers, and as such I want the current time.
It does not respond to the clock to give the current time when you click it.
In my opinion it should.
 
Thanks.
 

Fortunately, I solved various performance problems I had changing the machine, but now I run into a problem I don't have on the older computer.
The Preference window is to large, so I can't see the window's bottom and hence depress the OK button. This window is not resizable. That way , impossible to edit the preference, for instance enter my call !
My laptop is a small one, the screen is 1024x600. Of course, I tried to change these sizes, but no help. Even with 800x600. I opened the various conf file, but didn't find any topic concerning the Pref frame.

Hello,
Trying to get trx-control to talk with my TS-570. I'm using a usb to serial cable. Have set device to /dev/ttyUSB0, speed 57.600, databits 8 and no parity. Port is set to 4532. Poll to 500. Other settings are to default. Radio is 204.

Petr, is there a way to have the option for the QSO start/end time be "set by user" or "Set to now"?  Sometimes, i find that the QSO can go on for a bit and i'd like to be able to adjust time times without having to save the record.
Also, during my HRD ADIF import, it looks like all of the start/end times were set to zero minutes apart for each QSO.  Meaning if one Q started at 0700, the end time was 0700, while a different Q start time was 0730 and the end time was 0730.
Does this make sense?

I used CQRlog to participate in W1AW/8 here in West Virginia. CQRlog performed perfect. Not even a slight glitch.  100% awesome. CQRlog was very fast and never slowed.  The ability to enter a call have the 59 rst already there and just hit enter to log qso was great. Then to wipe call entry window by hitting the Esc key twice was invaluable.  Things went so smooth with CQRlog that the first night I logged 465 qso's in 3 hours. Fantastic! Then I was on RTTY for a lot of the event. And the link between fldigi and CQRlog was perfect.