Hi!
This problem has been there on older version,too. Just now I "blow my fuse" and also had a little time to investigate this.Today I have installed all updates for Fedora 19 to this Compaq mini Pc (1600MHz 2coreAtom). So everything should be up to date, also Cqrlog is 1.7.4.
Typing in a new qso is far too slow. You can not imagine to call cq and type in everything. You need to write on paper and then update cqrlog later.When call has been entered and you jump to another field (RST, Grid, Name) it takes 20-25 secs when you again can type in something.I tested also with another laptop Fujitsu Siemens (800Mhz 1core AMD, but it has SSD-hd) by copying everything to that machine. No rig and keyer connected (But they do not effect, I think) it takes 5-7sec dead time after jumping from call column to another column. I think this slower PC is faster because SDD-drive.
There is a work around for this bug and it can be reproduced every time with same procedure.
I'll start cqrlog so that it does not select log automaticly. I have to choose from logs I have. They all are small 500 - 1100 qsos.What ever log I choose after startup has the same delay when typing in a qso.
If I then CHANGE to another log, what ever I have there to select from, when it opens it accepts new qsos in faster. The delay for jumping from call colum to next column takes second, or less. So that you can really use it!
This happens always.Now, after todays study I know how to handle this bug but surely would like to see it fixed.
I did made debug dump from this with comment lines, but I do not upload it at this time as it is rather long and there are no clear signs from errors. Dumps are similar in bug's case and working case. Brief copy of dump:--------------------############ stopped here call has been typed in. Waiting to jump to next field #####################Nalezeno - W1AWSELECT * FROM view_cqrlog_main_by_qsodate WHERE callsign = 'W1AW' ORDER BY qsodate,time_onLoadForm: frmNewQSO########################## Stuck here for about 20-25secs. Nothing works !!!!!!!!!! ##############SELECT id_cqrlog_main FROM cqrlog_main WHERE adif=291 AND band='10M' AND ((qsl_r='Q') OR (lotw_qslr='L')) AND mode='SSB' LIMIT 1-----------------------
I can upload whole dump when/if requested.
Any similar problems ?
-- Saku, OH1KH
Tue, 2014-05-20 10:27
#1
Typing in qso is very slow
Hi Saku,
thank you for very good bugreport!
Could you send me please whole output with notes where it took so long? It would help me a lot. Do you have Super Check Partial window opened? It may slow down the computer when you have slower CPU.
73 Petr, OK2CQR
--
http://HamQTH.com/ok2cqr
https://ok2cqr.com
Sent to your email.
--
Saku
OH1KH
I made some more testing:
1) "Error connecting database" is still there! When starting cqrlog first time specially just after PC has started it is "normal" :( to get that error and there are no logs to select from log list.But it can happen also if PC has been on, and in use, but no cqrlog open.Just press cancel and start cqrlog again. Then, %95 sure, you get log list to select an continue usage. If not try again.
2) Exported all logs to adi. Deleted ~/.config/cqrlog directory (renamed) and started program. When it was creating first log got error ctyfiles/Exeptions.tab (missing?). Cancel stopped program. New start went ok. Imported logs and log settings.
3) found out that Database connect-utils-configuration-import does NOT import all settings from old log. Did not examine this, not the subject now. Just noticed that opening this new created log does not reload cw-keyer (no reload sound from keyer) as original log does. And thre are also other missing configs.
4)Tested with new logs and there is just the same delay. Enter call - jump to other field- type something and it appears after 10-15 secs.
5)Also same fix works. Open first log that you are not going to use. Then switch the log you are going to use and all works without delay. The first opened log is always delaying. After you have switched log one time all logs work without delay.
6)Same delay can be found as "double trouble" if you select window-qso list and then edit qso. It takes long time to get selected call to edit window, and another long time if you go to change some field . I tested with freqency, took long time to get the selecton list open. Fix for this is the same. Open another log, edit it, or directly came back to this log and everyting works without delays.
7)BTW there is no way to cancel qso edit. Just save qso or stop program. Where is the cancel-button?
Could it be some memory allocating issue that fixes itself on log switching?
-- Saku, OH1KH
--
Saku
OH1KH