Hi, thanks for the great app. Loving it, especially, the LOTW support.
There seems to be a bug with the new QSLR field introduced in 1.3.1.
The field is not updated for received LOTW QSLs for some reason. Please see the screenshot: http://goo.gl/BWAbd
Thanks,
Paul VA3PAW
Hi Paul et al,
The bug is also in 1.3.0 and a couple of days ago I emailed Petr with a screenshot of the problem. I guess he has his head down looking at it right now. Really good software package isn't it?
73 Graeme ZL2APV
Hi Graeme,
this is very strange. I use views in database for the lists in new qso and qso list windows. I have no idea why but is seems that this view doesn't update qslr field. I don't have this problem but I remember that when I was developing new version, the problem once appeard. Didn't find why it started to work again. I must do some research and I'll post here what I find.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Thanks Petr,
Let me know if I can do any testing for you. I guess it works for many others too or you would have probably had more posts on the problem.
73, Graeme ZL2APV
Hi Petr,
Thank you. I was wondering if this may be an upgrade problem. Meaning, when I downloaded and installed new 1.3.0 / 1.3.1 .deb package (versions) over existing 0.9 version, the firebird db views were not properly updated for some reason?
Either way, I exported configuration to file, then uninstalled the app and deleted the ~/.config/cqrlog folder.
Then, I reinstalled 1.3.1 from repository, imported config (did not work...bug?), set up to use local mysql db (with root), imported latest adif backup and qslr field now seems to work finally!
I see from the console that you are updating that field. Do you think it would rather make sense to make it computed (virtual) column? Or compute it in a view instead based on values in QSL_R/EQSL_R/LOTW_R fields?
I also noticed that when I imported my ADIF backup into a new log, information in the Power (pwr) field disappeared (bug?).
Also, when the import completed, and I clicked OK, the program crashed with the following message in the console:
TApplication.HandleException qCQRLOG : Field not found : "id_cqrlog_main"
Then, after a restart, everything was okay.
Also, when I close the program, I always see unhandled exception when 'Closing ini file...' - please see below (bug?):
120304 21:35:20 [Note] /usr/sbin/mysqld: Normal shutdown
120304 21:35:20 InnoDB: Starting shutdown...
Closing ini file ...
An unhandled exception occurred at $08071A45 :
EAccessViolation :
$08071A45
$08186555
That's it for today :-)
Thank you,
73, Paul
Hi Paul,
this is interesting, I see this for the first time. Maybe there is a bug, I tried to import config file from version 0.9.6 into version 1.0 and never into newer version.
QSLR field which should put QSL_R, EQSL_QSL_RCVD and LOTW_QSLR together is virtual field. It is create in the view_cqrlog_main_order_by_date. It is much easier than creting that field in database and do all updates on it.
Power disappeared? I'll check it. Thank you.
Maybe the access vilation is caused by importing old ini file, I don't know. Field id_cqrtlog_main is very important and used all over the cqrlog source code.
I know about that error after program is closed. I tried to use gdb or tried to add some debug messages to log and it seems that problem is somewhere in desctructors of objects. But I have no idea which object has the problem. It is somewhere very deep in source code of GTK libraries. Maybe later I'll find solution.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Hi Petr,
I am not sure if you have fixed this bug in your new 1.3.2 release as I will wait for the update to your ppa and get it from there but if not here is another clue.
Receiving a qsl from lotw does not update the qslr field but if I receive a subsequent eqsl then the field updates both eqsl and lotw. Eqsl's update the field correctly every time regardless of whether there was an lotw qsl or not.
73, Graeme ZL2APV
Hi Greame,
finally, I know where is a bug. Now I have to fix it. Problem is with eqsl field. It seems that default value is NULL and CONCAT returns null when one of the fields is null (QSLR is only "virtual" field created from qsl_r,lotw_qslr and eqsl_qsl_rcvd fields).
Thank you for your help!
73 Petr
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Hi Petr,
Glad I could make some small contribution. I will leave it in your capable hands.
73, Graeme