Using Ubuntu 24.04 and CQRLog Ver. Alpha (136) QT6 and QRZ Callbook support.
When I do a "Callbook => Database Update", it hangs when it tries to update a QSO where dxcc_ref = !. Unfortunately, that means it hangs whenever it comes across a "/MM" call or several other variants.
It should timeout when it gets a bad call, etc, and just move to the next QSO to update.
As always, thanks for the great program! I was talking it up in the Linux booth at the Dayton Hamvention!
-David, N9KT
Hi David!
Exported my /MM qsos to test log and I can see a hang.
Cancel button does not work, but top right corner X closes update window. How ever it leaves open transaction that prevents second try.
I will look this when time permits. There is something that needs fixing.
I did not get what means "dxcc_ref = !" as with quick look "dxcc_ref" seems to be a table name, not a database column having "!" value. (??)
/MM how ever gives something to fix first. Then I have to think what "!" means.
--
Saku
OH1KH
Here's where I see dxcc_ref = !
-David, N9KT
Thanks, got it!
It is not directly referred cqrlog_main column. Named "DXCC" in preferences/Visible columns.
Seems to be "!" in all my /MM qsos, now when I set it visible.
I think I found a reason and fix for this. Seems to work at least with my /MM qsos.
I sent you a PM to QRZ address.
--
Saku
OH1KH