Rsclub2_2andClaude Fable 5.1 78de8b0a9c fix: suppress automatic DX cluster spots for worked stations (#91) ...

Automatic spots from directional opportunities were generated without
looking at the worked state, so stations already in the log kept being
spotted to the connected loggers.

The spot block in MessageBusManagementThread now asks
isAlreadyWorkedForDxClusterSpot(sender) before broadcasting. The rule:

- the band is taken from the sender's known frequency via
  FrequencyTextParser; an unknown band keeps the previous behaviour;
- the per-band worked flag of that band suppresses the spot
  (ChatMember.isWorkedOnBand maps B_1296/B_2320/B_5760 to the
  historically named worked1240/worked2300/worked5600 flags);
- the global worked flag suppresses the spot only when no per-band
  flag exists at all (Simplelogfile source without band information);
- the global flag together with per-band flags for other bands does
  not suppress, because the per-band information is authoritative.

Suppressed spots are logged at FINE. The direction check, the
inAngleAndRange marker, the tick sound and manual spots from the map
window and the settings test spot are unchanged.

Fixes #91

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-10-11 01:12:02 +02:00

..

src

fix: suppress automatic DX cluster spots for worked stations (#91)

2026-10-11 01:12:02 +02:00

build.gradle.kts

Next major release/version1.50 (#89)

2026-10-08 23:22:11 +02:00