…Os (#903, #906) Previous fix rejected the import entirely when logN<=0, which caused all QSOs to be lost. This revision falls back to getMaxLogNumber() so QSOs are always imported into a valid log. Root cause of #906: SetupPageLogs::slotAnalyzeNewLogData() did not update selectedLog after addNewLog() succeeded, leaving it at -1. When the setup dialog closed, mainwindow set currentLog=-1, and the next ADIF import stored every QSO with lognumber=-1 in the database. Fix #903: adifReadLog() now calls getMaxLogNumber() when logN<=0 and uses the returned ID as the target log; returns -3 only if no logs exist. Fix #906: slotAnalyzeNewLogData() calls getMaxLogNumber() after a successful INSERT to keep selectedLog consistent with the newly created log, so getSelectedLog() returns a valid value from that point on. Tests: add three regression tests in tst_filemanager — - valid logN stores correct lognumber in the DB - invalid logN falls back to existing log (no lognumber=-1 rows) - getMaxLogNumber() returns >0 when at least one log exists https://claude.ai/code/session_012nVDvt6JxTPvadmorSRX1r

On ADIF import, lognumber in table log of imported QSOs are set -1. #903

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions