Skip to content

Resolve DXCC country when live-logging FT4 and Terminal QSOs - #180

Merged
magicbug merged 1 commit into
mainfrom
cursor/fix-live-qso-dxcc-country-c96b
Oct 22, 2026
Merged

magicbug merged 1 commit into
mainfrom
cursor/fix-live-qso-dxcc-country-c96b

Conversation

@magicbug

Copy link
Copy Markdown
Owner

Problem

FT4 and Terminal QSOs logged automatically via LiveQsoLogger were persisted without Dxcc and Country, so the logbook Country column stayed empty and ADIF export omitted COUNTRY until background backfill ran. Manual logbook entry already resolved DXCC at save time via QsoLogbookViewModel.ResolveDxccFields.

Fix

  • Inject IDxccLookupService into LiveQsoLogger and populate Dxcc / Country on QsoRecordCreateRequest before AddQsoAsync.
  • Open logbook views already subscribe to IQsoLogbookRepository.QsosChanged, which AddQsoAsync raises, so the list refreshes without a restart once country is stored on the new row.

Tests

  • Added LiveQsoLoggerTests covering DXCC persistence, unresolved callsigns, and QsosChanged notification.
  • Full OscarWatch.Tests suite passes locally.

Fixes #179

Open in Web Open in Cursor 

LiveQsoLogger now uses IDxccLookupService when building QsoRecordCreateRequest,
matching the manual logbook path so Country and ADIF DXCC are stored immediately.

Fixes #179

Co-authored-by: Peter Goodhall <magicbug@users.noreply.github.com>
@magicbug
magicbug marked this pull request as ready for review October 22, 2026 10:32
@magicbug
magicbug merged commit f16d134 into main Oct 22, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: FT4/Terminal auto-logged QSOs saved without DXCC/Country

2 participants