From 0ad0d25c702846a4b69cc3caa4607118502dcbf5 Mon Sep 17 00:00:00 2001 From: Ian Renton Date: Fri, 18 Sep 2026 17:14:24 +0100 Subject: [PATCH] Add QRP and RaDAR Rally activities --- core/constants.py | 16 ++++++++++++++++ data/activity.py | 3 ++- 2 files changed, 18 insertions(+), 1 deletion(-) diff --git a/core/constants.py b/core/constants.py index 8e1f934..8d51f37 100644 --- a/core/constants.py +++ b/core/constants.py @@ -44,6 +44,14 @@ ACTIVITIES = [ icon="fa-moon", refs_globally_unique=False, ), + Activity( + name="QRP", + comment_names=["QRP"], + description="Low power", + sig_type=ActivityType.TRADITIONAL, + icon="fa-volume-low", + refs_globally_unique=False, + ), Activity( name="POTA", comment_names=["POTA"], @@ -257,6 +265,14 @@ ACTIVITIES = [ icon="fa-square", refs_globally_unique=False, ), + Activity( + name="RaDAR Rally", + comment_names=["RaDAR"], + description="RaDAR Rally", + sig_type=ActivityType.EVENT, + icon="fa-headset", + refs_globally_unique=False, + ), Activity( name="WAB", comment_names=["WAB"], diff --git a/data/activity.py b/data/activity.py index 4fd0ca0..dd5d6f1 100644 --- a/data/activity.py +++ b/data/activity.py @@ -25,7 +25,8 @@ class Activity: # anything else we expect a user to put in a spot comment, and therefore we can pull references out of # spot comments without also needing to see the activity name first. For example, "OHFF-1234" or "B/G-1234" are # obviously WWFF and WWBOTA, nothing else looks like those. But "SZ09" could be WAB or Tiles, "GB1234" could - # conceivably be POTA or ILLW, etc. + # conceivably be POTA or ILLW, etc. So in those cases we need to see the name of the activity itself immediately + # before it. refs_globally_unique: bool # Activity names as they might appear in cluster spot comments, e.g. ["TOTA"] comment_names: list[str] = field(default_factory=list)