CQRLOG - bugs

Grayline is 1 hour off when using "get UTC time from computer"

This is an old bug, nothing to do with 1.5.5.

I prefer to use the "get UTC time from computer" option, because it takes the DST into consideration. However, the grayline window is one hour behind the real sunrise/sunset.

You can use the manual setting UTC 3, grayline 2 and sunrise/set 3 to get also the grayline correct, but then you have to remember to change the settings twice a year.

73 de Pekka oh2bsc

Forums: 

Band map

Hi, after update to 1.5.5
I still have this same preferences and i cant see any spots in Band map window. :(

When i send sh/dx 100 and when spots are comming from telnet window.
Band map windows is still blank.

Maybe this is only my problem ??

73! Pawel SQ5LTL

Forums: 

Possible memory leak

This is just a heads up. Yesterday there was an upgrade for MySQL on Ubuntu and since then I had an error message after running CQRLog most of the day that MySQL had stopped. Later I was doing my incoming QSL cards and after about 100 cards the machine got slower and slower and finally I had to exit. I was not sure if the Loging was the problem and did not take any memory measurements but if others note any problems that seem related then a bug (probably MySQL) should be posted.
 
73, Graeme ZL2APV

Forums: 

CQRLog doesn't kill rigctld

I am unsing 1.53 (tarball verson) under opensuse 12.1.I have "Run rigctld when program starts" checked.Rigctld does start, but when I exit CQRLog using the File --> Close menu, rigctld is not killed.
This an example of checking for running processes after CQRLog exits:
32404 ?        S      0:00 /usr/bin/rigctld -m 313 -r /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AH01D7H3-if00-port0 -t 4532
I amnot sure what other info you might need. If you'll let me know I'll try to get it to you.
 
Thanks

Forums: 

Database crash

Hello,
After using this software for many months only TWO things annoy.
 
1) On closing it does not save the window settings to keep 'Always on top', I have to re- click the 'window on top' setting every time I start the program.
 
2) Pretty much every day at some point, I click on a bandmap spot and I get an error message saying theres a database error and I can either click OK top carry on and 'risk data corruption' or Cancel to close the program. I always have to re-start the program, as art that point from then on the cluster/bandmap does not work.

Forums: 

FLdigi QSO start time

Currently it seems that only the QSO end time is being pulled from the FLdigi log, and that time is being used for both the start and end times in CQRlog. The start time is in FLdigi's log as well, and should be pulled from that log when the other information is. It's not as big a deal with short QSOs, but with a longer QSO it can mean the difference between LoTW QSLs working or not working.
 
There's a thread about this in the "open discussion" forum, but it really belongs here.
 

Forums: 

Pages

Subscribe to RSS - CQRLOG - bugs