feat(appearance): colour log rows by QSL status, and fix UDP QSO numbering

New Settings → Appearance section: whole-row colouring in the log grid driven by QSL / LoTW state, each rule with its own colour from a palette or a free picker. What Logger32 does, with one difference that matters — the colour is applied as a 24% tint, not a fill. Logger32's grid is white; this one is dark, and a saturated user-picked colour behind white text is unreadable at exactly the moment the operator is scanning for what still needs sending. Rules are ORDERED and the first match wins, because a contact is usually several of these at once: one confirmed on LoTW and by card is confirmed, not "sent, awaiting reply". The order lives in the data so the panel can show the rules in the order they actually apply, numbered. The colour is interpolated into a CSS color-mix(), so anything that is not plainly #rrggbb is refused on the way in and falls back to the default. Also fixes the QSO number column, which was empty for contacts logged from WSJT-X: that path inserts through the repo directly and never reached AddQSO. Rather than chase each of the remaining bulk-insert paths — the POTA hunter import and the LoTW/QRZ "add what I was missing" passes, which insert OLD dates and so shift every number after them — the index now checks its length against a COUNT and rebuilds when they disagree. One indexed count beats remembering to invalidate in a place that does not exist yet.
2026-08-13 01:06:21 +02:00
parent 2484cd2515
commit 858c04d267
13 changed files with 378 additions and 7 deletions
@@ -0,0 +1,38 @@
+// Row colouring for the log grid, by QSL / LoTW status.
+//
+// The rules are ORDERED and the first match wins: a contact is usually several
+// things at once, and one confirmed on LoTW and by card is confirmed, not
+// "sent, awaiting reply".
+
+export type RowColorRule = { id: string; color: string; enabled: boolean };
+export type RowColorSettings = { enabled: boolean; rules: RowColorRule[] };
+
+// ADIF QSL fields are single letters. Y is the only one that means "yes";
+// R (requested) and Q (queued) mean a card is owed, which is a different state
+// and the one an operator is looking for when deciding what to post.
+const yes = (v: any) => String(v ?? '').trim().toUpperCase() === 'Y';
+const owed = (v: any) => {
+  const s = String(v ?? '').trim().toUpperCase();
+  return s === 'R' || s === 'Q';
+};
+
+export function matchRowRule(q: any): string | null {
+  if (!q) return null;
+  if (yes(q.lotw_rcvd)) return 'confirmed_lotw';
+  if (yes(q.qsl_rcvd) || yes(q.eqsl_rcvd)) return 'confirmed_paper';
+  if (yes(q.qsl_sent) || yes(q.lotw_sent) || yes(q.eqsl_sent)) return 'sent_waiting';
+  if (owed(q.qsl_sent)) return 'to_send';
+  return null;
+}
+
+// The colour is applied as a TINT, not a fill. The grid is dark and a solid
+// user-picked colour behind white text is unreadable at exactly the moment it
+// matters — Logger32 gets away with it because its grid is white.
+export function rowStyleFor(q: any, cfg: RowColorSettings | null): { backgroundColor: string } | undefined {
+  if (!cfg?.enabled) return undefined;
+  const id = matchRowRule(q);
+  if (!id) return undefined;
+  const rule = cfg.rules?.find((r) => r.id === id);
+  if (!rule?.enabled || !rule.color) return undefined;
+  return { backgroundColor: `color-mix(in srgb, ${rule.color} 24%, transparent)` };
+}