¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

QSO ID and Alert beep


 

Hi to all,
As I am looking for an alternative to cqrlog, I am currently testing Qlog and it looks quite promising.
Two questions.
After importing the adif file, the newest QSO in the log receives QSO# (or QSO ID) = 1 and oldest QSO gets the highest QSO#. Logically and practically, shouldn't it be the other way around - QSO ID = 1 for oldest QSO in the log? IMHO, yes.

Alert beep doesn't seem to work on either Windows or Linux. Or I'm doing something wrong...


 

Hi.

QSO IDs are assigned based on the order in which the QSOs are inserted into the database. This means that the QSO ID corresponds to the order in your ADIF file. QLog then orders the QSOs based on the start time. Therefore, if your ADIF export has a different order, the QSO IDs can be in a different order as well. Please, keep in mind that the QSO ID is an internal parameter and it is only up to QLog how it handles this parameter.

Alert beep is explained here -

Regards
Ladislav


¨²t 4. 6. 2024 v?14:19 odes¨ªlatel Slav, EI6KW via <sp3rxo=[email protected]> napsal:

Hi to all,
As I am looking for an alternative to cqrlog, I am currently testing Qlog and it looks quite promising.
Two questions.
After importing the adif file, the newest QSO in the log receives QSO# (or QSO ID) = 1 and oldest QSO gets the highest QSO#. Logically and practically, shouldn't it be the other way around - QSO ID = 1 for oldest QSO in the log? IMHO, yes.

Alert beep doesn't seem to work on either Windows or Linux. Or I'm doing something wrong...