When logging a contact focus is shifted to status of upload window for about 6 seconds before you can start typing a call. not very good when working the pileups.
Clublog upload is slow, when i import a file with x new log entries it takes a few seconds for each entry to be uploaded.
Regin, OY1R
Hi Regin!
How is your internet connection? Have you tested with https://www.speedtest.net ?
It will effect at least clublog update.
If you open console and give command:
top
While you operate (cqrlog running) you can see what is taking resources.
Look at
"load average", should be around (or less) than 1
"Mib Swap / used" If you have enough RAM memory the used swap should be rather low compared to total.
"PID list / %CPU" shows how programs use cpu.
In my laptop cqrlog and wsjtx are using around %5 cpu. At the time of qsjt decode process "jt9" takes around %45-%99
You can focus to cqrlg with command:
top -d0.1 -H -p$(pidof -s cqrlog)
Then you may see some spikes %10 - %80 but they should not last long.
How that does look like?
--
Saku
OH1KH
1:
i have relatively fast internet, vdsl2+ 100/20mbps testing at ~95/23mbps
2:
load is 0.5, cpu usage idle 0 and 1% peak ~8-10%
3:
also when i log a qso the program somtimes starts to upload qso's that have been uploaded before. if i restart the program and log a contact it starts uploading old qsos again. i have to manually "mark all qso's as uploaded to all logs"
4:
crashes when scrolling in the qso list
Hi !
From the point 4 I can see that you have rather old version. It is long time since the qsl list scrolling was fixed.
Can you compile from source?
In that case you could get latest source from Petr's GitHub https://github.com/ok2cqr/cqrlog
If not you can visit my GitHub page https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled read the README and consider could you try with the alpha test binary.
At least it should fix the 4) issue.
--
Saku
OH1KH