开云体育

I prefer to set the width manually and have it stay that way rather than having it automatically adjust to the content. I hope other users like that concept and approve of the change if you make it.

That's an interesting side effect. It shows that a developer can never anticipate everything down to the last detail. Thanks for sharing your experience. so 14. 9. 2024 v 14:26 odesílatel Michael

Here I would say that it is not an issue but a feature. With each table update, the width of all columns is evaluated and set according to the longest item in the given column. If this shouldn't

Ok I found my answer.? I had enabled 'QSO Wiping' on my Rig setup for some reason and in WSJT-X I had 'Fake It' enabled for Split.? So when I would transmit it changed the frequency and wiped the

Nevermind I was wrong even if I had worked the station previously it still wipes.

I've noticed one oddity since 0.38 when I engage in a contact with a station on WSJT-X I see the callsign lookup in qLog like before but then it clears away if I have never worked the station before,

I have experienced #4 as well. I don’t have near the log this size but I just deleted one of the QSOs then let LoTW download again. But would be nice to just update all the entries.

1. Backup is longish at 70K QSO but I live with it, I'd actually prefer the backup at exit rather than startup though ;-) I am usually less worried about shutdown time than start up time. 2. Works OK

I don't know how Log4OM behaves with such a volume, but I know how QLog behaves - it is not fast enough for comfortable work. Based on your emails, I tried to look into areas where improvements could

Not really looking for any bug fixes or new features, just some observations and suggestions. Qlog 0.37.2 (built from source, yes I need to upgrade) O/S Manjaro Linux KDE HP Laptop 8th gen i7 with 32

I'm at 70K QSO nearly and it's still going OK, I would venture to say it works better than Log4OM with the same number of QSO. And Log4OM using the same backend. HRD was a dog even at 50K QSO. The

Same issue here. Qlog v 0.38.0 Linux Mint 21.2 Cinnamon The name field width seems to be the culprit for me.

I looked at the code over the weekend and there are many possibilities to improve the performance. Unfortunately, if you have 1M QSOs, you are not a target group for QLog. QLog was designed as a

Hi Ladislav I notice when I set the column widths in the QSO table, the columns do not stay as intended (or as set). My o bservation is that that any text contained in the field affects the width of

Hello Robert, That's what I'm using on my Windows machine, home-made. 73 Norby

Norby, If you have over a million contacts to put it a database, you need a client server database. The only logbook I know of that uses a client server model would be CQRLOG, https://www.cqrlog.com/

Thank you for the explanations and hints. I think that QLog would not fit my needs in the long run, as I have another 1 million contacts to import, even though spread across 130 logs. I'll continue to

Deselecting the >>MODE<<? option in the Rig Settings has made a world of difference when using a Yaesu transceiver when allowing QLog to communicate with the radio from the DX Spot window.

One thing you may can try is to create a custom QSO Filter to limit the contacts. My log is way smaller than yours only about 22,000 entries. I created a filter like this that limits to just QSOs this

This is something I would also like to see implemented in QLog. Regards, Diego