diff --git a/docs/PROJECT_CONTEXT.md b/docs/PROJECT_CONTEXT.md index 6ebd4130..32a3cef0 100644 --- a/docs/PROJECT_CONTEXT.md +++ b/docs/PROJECT_CONTEXT.md @@ -70,11 +70,16 @@ CR/LF framing, XML framing, ports/transports, callsign normalization and frequen - The Simplelogfile interpreter reads the selected text file after connection startup and then once per minute using a fixed built-in callsign pattern. - Simplelogfile callsigns are normalized to base callsigns and set only the global Worked state for every active variant. They do not create per-band Worked or grid-square state. - Simplelogfile-derived Worked state is not persisted in SQLite. The selected file is the durable source and is read again in each application session. -- The interpreter only adds positive runtime marks. It does not remove existing marks during the current session and does not reset automatically when a new contest starts. +- The interpreter only adds positive runtime marks. It does not remove existing marks during the current session and does not reset automatically when a new contest starts. A database reset does not modify the file; callsigns contained in it are marked as worked again during the next periodic evaluation. - A missing selected file is created. Read, path and creation failures are contained so the periodic timer remains alive; successful creation triggers a one-time, non-blocking UI notice with the exact path and setup/contest checks. - Network-derived and manually assigned Worked, NOT-QRV and worked-grid state continues to use SQLite with its established lifetime and reset behaviour. - Automatic QRG updates require both an enabled source and valid incoming `RadioInfo` or Win-Test `STATUS` data. Merely enabling a source does not provide or validate a current QRG. +### Terrain data providers + +- The active terrain profile provider is Open-Meteo using Copernicus GLO-90 data. +- `OfflineDemImportService` only prepares a local directory and copies manually selected Copernicus GLO-30 GeoTIFF files into it. Importing files does not activate an offline provider or change the active calculation chain. + ### ON4KST session and authentication - One KST4Contest connection authenticates one ON4KST TCP session with one local login callsign and one password. diff --git a/github_docs/de-AirScout-Integration.md b/github_docs/de-AirScout-Integration.md index 9716061e..8071d5b0 100644 --- a/github_docs/de-AirScout-Integration.md +++ b/github_docs/de-AirScout-Integration.md @@ -2,7 +2,7 @@ > 🇬🇧 [English version](en-AirScout-Integration) | 🇩🇪 Du liest gerade die deutsche Version -AirScout (von DL2ALF) ist ein Programm zur Erkennung von Flugzeugen für den Aircraft-Scatter-Betrieb. KST4Contest ist eng mit AirScout integriert und zeigt reflektierbare Flugzeuge direkt in der Benutzerliste an. +AirScout (von DL2ALF) berechnet Aircraft-Scatter-Gelegenheiten anhand aktueller Flugzeugpositionen. KST4Contest übernimmt diese Ergebnisse und zeigt für die jeweilige Gegenstation geeignete Flugzeuge direkt in der Benutzerliste an. > **Aircraft Scatter** ermöglicht sehr weitreichende Verbindungen auf VHF und höher – auch für Stationen mit geringer Höhe über NN oder ungünstigen topografischen Verhältnissen. @@ -15,9 +15,9 @@ Download von AirScout: --- -## Flugzeugdaten-Feeds (ADSB) +## Flugzeugdaten-Feeds (ADS-B) -Öffentliche Flugzeugdaten-Feeds im Internet sind oft unzuverlässig und begrenzt nutzbar. Eine empfohlene Alternative bietet **OV3T (Thomas)** mit einem dedizierten ADSB-Feed-Dienst: +Öffentliche Flugzeugdaten-Feeds im Internet sind oft unzuverlässig und nur eingeschränkt nutzbar. Eine empfohlene Alternative bietet **OV3T (Thomas)** mit einem dedizierten ADS-B-Feed-Dienst: - https://airscatter.dk/ - https://www.facebook.com/groups/825093981868542 @@ -28,7 +28,7 @@ Für diesen Dienst ist ein Account erforderlich. Bitte eine Spende für Thomas i ## AirScout einrichten -### Schritt 1: ADSB-Feed in AirScout konfigurieren +### Schritt 1: ADS-B-Feed in AirScout konfigurieren 1. AirScout starten. 2. In den AirScout-Einstellungen den OV3T-Feed-Account eintragen (Benutzername, Passwort, URL). @@ -85,32 +85,40 @@ Andernfalls kann es zu fehlerhaften AP-Daten kommen. ## AP-Spalte in der Benutzerliste -Nach der Einrichtung erscheint in der Benutzerliste eine **AP-Spalte** mit bis zu zwei reflektierbaren Flugzeugen pro Station. +Nach der Einrichtung erscheint in der Benutzerliste eine **AP-Spalte**. Sie zeigt für jede Station die Ankunftszeit und das von AirScout berechnete Reflexionspotenzial der ersten beiden geeigneten Flugzeuge. Beispiel-Darstellung: | Station | AP-Info | |---|---| -| DF9QX | 2 Planes: 0 min / 0 min, je 100% | -| F5DYD | 2 Planes: 14 min / 31 min, je 50% | +| DF9QX | 0 (100 %) / 0 (100 %) | +| F5DYD | 14 (50 %) / 31 (50 %) | + +Die Zahl vor der Klammer gibt die verbleibenden Minuten bis zur berechneten Gelegenheit an. Die Prozentzahl beschreibt das von AirScout gemeldete Reflexionspotenzial. Sie ist keine QSO-Wahrscheinlichkeit. Die AP-Informationen sind auch im **Privatnachrichten-Fenster** verfügbar. -Die Prozentzahl gibt das Reflexionspotenzial an (Größe des Flugzeugs, Höhe, Entfernung). +## Einfluss auf Priority Score und Timeline + +Mindestens ein von AirScout als erreichbar gemeldetes Flugzeug erhöht den Priority Score der Station. Eine unmittelbar bevorstehende Gelegenheit in null, einer oder zwei Minuten wird zusätzlich zeitabhängig gewichtet. AirScout ist dabei nur ein Faktor neben Worked-Status, verfügbaren Bändern, QRB, Antennenrichtung, Chat-Aktivität und Skeds. + +Die AP- und Sked-Timeline verwendet den Priority Score zur Auswahl interessanter Stationen und ordnet die nächste geeignete Aircraft-Scatter-Gelegenheit zeitlich ein. Das Reflexionspotenzial bestimmt zusätzlich die Darstellung des AP-Symbols. Die Timeline bleibt eine Vorschau; sie garantiert kein QSO. --- ## AP-Variablen in Nachrichten -Die Flugzeugdaten können direkt in Nachrichten eingefügt werden: +Die Flugzeugdaten der ausgewählten Station können direkt in Shortcuts, Snippets und andere stationsbezogene Nachrichten eingefügt werden: - `FIRSTAP` → z. B. `a very big AP in 1 min` - `SECONDAP` → z. B. `Next big AP in 9 min` Details: [Makros und Variablen](de-Makros-und-Variablen#variablen) +Da die Werte eine ausgewählte Gegenstation benötigen, stehen `FIRSTAP` und `SECONDAP` nicht als globale Beacon-Variablen zur Verfügung. + --- ## „Show Path in AirScout"-Button -In der Benutzerliste gibt es einen Button mit einem Pfeil, der die Richtung (QTF) zur ausgewählten Station anzeigt. Ein Klick maximiert AirScout und zeigt den Pfad mit reflektierbaren Flugzeugen zum ausgewählten Gesprächspartner. +In der Benutzerliste gibt es einen Button mit einem Pfeil, der die Richtung (QTF) zur ausgewählten Station anzeigt. Ein Klick maximiert das externe AirScout-Fenster und lässt dort den Pfad zur ausgewählten Gegenstation mit den berechneten Aircraft-Scatter-Gelegenheiten anzeigen. Die Schaltfläche startet keine eigene Gelände- oder Ausbreitungsberechnung in KST4Contest. diff --git a/github_docs/de-Changelog.md b/github_docs/de-Changelog.md index c4d6949f..2d7c9d1a 100644 --- a/github_docs/de-Changelog.md +++ b/github_docs/de-Changelog.md @@ -34,6 +34,8 @@ v1.42 führt mehrere bisher getrennte Auswertungen zusammen. Bandinformationen, - **Manuelle QTF-Eingabe:** Die aktuelle Antennenrichtung kann auch ohne PSTRotator direkt in KST4Contest geändert werden. +- **Nachrichtenvariable `MYQTF`:** Die aktuelle Antennenrichtung kann als numerischer Winkel in Grad in Shortcuts, Snippets und andere unterstützte Nachrichtentexte eingesetzt werden. + - **Filter zurücksetzen:** Ein eigener Reset-Button entfernt die aktiven Filterprädikate der Benutzerliste zuverlässig. - **Kartencluster:** Räumlich dicht beieinanderliegende Stationen werden bei niedrigen Zoomstufen zusammengefasst. Die ausgewählte Station und relevante Richtungsgelegenheiten bleiben einzeln sichtbar. @@ -80,7 +82,7 @@ v1.42 führt mehrere bisher getrennte Auswertungen zusammen. Bandinformationen, - **DXLog-Gesamtlog übernommen:** Der UCXLog-kompatible UDP-Listener verarbeitet neben `contactinfo` auch `contactreplace`. Dadurch kann ein von DXLog.net als vollständiges Log ausgesendeter Datenbestand eingelesen werden. -- **Simplelogfile-Verhalten präzisiert:** Die ausgewählte Textdatei wird einmal pro Minute mit einem festen Rufzeichenmuster ausgewertet. Treffer setzen den globalen Worked-Status aller aktiven Varianten des Basisrufzeichens, werden aber nicht in SQLite persistiert. Eine fehlende Datei wird angelegt; Lese- und Erstellungsfehler beenden die periodische Auswertung nicht. +- **Simplelogfile-Verhalten präzisiert:** Die ausgewählte Textdatei wird einmal pro Minute mit einem festen Rufzeichenmuster ausgewertet. Treffer setzen den globalen Worked-Status aller aktiven Varianten des Basisrufzeichens, werden aber nicht in SQLite persistiert. Eine fehlende Datei wird angelegt; Lese- und Erstellungsfehler beenden die periodische Auswertung nicht. Ein Datenbank-Reset verändert die Datei nicht, sodass enthaltene Rufzeichen bei der nächsten Auswertung erneut als gearbeitet markiert werden. - **Automatische QRG-Übernahme abgesichert:** `MYQRG` wird nur von einer aktivierten Schnittstelle aktualisiert, die tatsächlich gültige `RadioInfo`- beziehungsweise Win-Test-`STATUS`-Pakete liefert. Eine aktivierte, aber nicht liefernde Quelle ersetzt die notwendige Funktionsprüfung oder manuelle QRG-Pflege nicht. @@ -415,7 +417,6 @@ Erste öffentlich veröffentlichte Version. Grundfunktionen: ## Geplante Features -- `MYQTF`-Variable (eigene Antennenrichtung als Text) - ~~Lebensdauer für den Worked-Status (automatisches Zurücksetzen)~~ ✅ **Umgesetzt in v1.40** (3-Tage-Lebensdauer, kein manuelles Zurücksetzen mehr nötig) - Filterung des „Cluster & QSO der anderen"-Fensters auf eigenes QTF - Weitere Topografie-basierte Berechnungen für die Richtungswarnung diff --git a/github_docs/de-Funktionen.md b/github_docs/de-Funktionen.md index de6cd8ff..c2eb82b7 100644 --- a/github_docs/de-Funktionen.md +++ b/github_docs/de-Funktionen.md @@ -207,7 +207,7 @@ Im Klartext: Ein erkannter Hinweis bedeutet „wahrscheinlich auf diesem Band ak Worked-, NOT-QRV- und Großfeldinformationen aus den Netzwerkschnittstellen sowie manuelle Markierungen werden in der internen SQLite-Datenbank gespeichert und beim nächsten Start wieder geladen. Die Einträge laufen nach drei Tagen automatisch ab. Ein Reset vor jedem Contest ist deshalb normalerweise nicht erforderlich. -Simplelogfile-Treffer sind davon ausgenommen. Sie werden nicht in SQLite persistiert, sondern bei jedem Programmlauf aus der ausgewählten Datei abgeleitet. Die Datei ist damit die dauerhafte Quelle. Der Interpreter entfernt während der laufenden Sitzung keine bereits gesetzte Worked-Markierung und setzt den Zustand beim Wechsel zu einem neuen Contest nicht automatisch zurück. +Simplelogfile-Treffer sind davon ausgenommen. Sie werden nicht in SQLite persistiert, sondern bei jedem Programmlauf aus der ausgewählten Datei abgeleitet. Die Datei ist damit die dauerhafte Quelle. Der Interpreter entfernt während der laufenden Sitzung keine bereits gesetzte Worked-Markierung und setzt den Zustand beim Wechsel zu einem neuen Contest nicht automatisch zurück. Ein manueller Datenbank-Reset verändert oder leert die Datei ebenfalls nicht. Darin enthaltene Rufzeichen werden bei der nächsten Auswertung innerhalb einer Minute erneut als gearbeitet markiert. Ein manueller Reset unter **Workedstn database** entfernt sämtliche Worked-Markierungen, NOT-QRV-Tags und gespeicherten Worked-Großfelder. Die bekannten Rufzeichenzeilen bleiben dabei in der Datenbank erhalten. Einzelheiten: [Worked Station Database Settings](de-Konfiguration#worked-station-database-settings-gearbeitete-stationen-datenbank). @@ -523,7 +523,7 @@ UDP selbst bestätigt außerdem keine Paketzustellung. Bleibt die QTF unverände Im Klartext: KST4Contest liefert die Zielrichtung und verarbeitet die gemeldete Position. Die mechanische Realität bleibt Aufgabe des Rotators – und gelegentlich der Blick aus dem Fenster. -Konfiguration und Portbelegung: [Konfiguration – PSTRotator-Einstellungen](de-Konfiguration#pstrotator-einstellungen-ab-v131-vollstaendig-konfigurierbar-ab-v140). +Konfiguration und Portbelegung: [Konfiguration – PSTRotator-Einstellungen](de-Konfiguration#pstrotator-einstellungen-ab-v131-vollständig-konfigurierbar-ab-v140). --- diff --git a/github_docs/de-Konfiguration.md b/github_docs/de-Konfiguration.md index 348a54fc..3113f4d0 100644 --- a/github_docs/de-Konfiguration.md +++ b/github_docs/de-Konfiguration.md @@ -109,7 +109,7 @@ Drei Methoden stehen zur Verfügung, um gearbeitete Stationen automatisch zu mar ### Universal File Based Callsign Interpreter (Simplelogfile) -Liest die ausgewählte Textdatei einmal pro Minute mit einem fest eingebauten Rufzeichenmuster. Die Treffer werden auf Basisrufzeichen normalisiert und setzen für alle aktiven Varianten nur den globalen Worked-Status. Band- und Locatorinformationen können daraus nicht abgeleitet werden. Die Funktion eignet sich als Fallback für Logprogramme ohne unterstützte Netzwerkschnittstelle. +Liest die ausgewählte Textdatei einmal pro Minute mit einem fest eingebauten Rufzeichenmuster. Die Treffer werden auf Basisrufzeichen normalisiert und setzen für alle aktiven Varianten nur den globalen Worked-Status. Band- und Locatorinformationen können daraus nicht abgeleitet werden. Die Funktion eignet sich als Fallback für Logprogramme ohne unterstützte Netzwerkschnittstelle. Vor der Verwendung sollte deshalb geprüft werden, ob das eingesetzte Logprogramm bereits eine der unterstützten Netzwerkschnittstellen bereitstellt. Existiert die ausgewählte Datei noch nicht, legt KST4Contest sie an und zeigt einmalig den vollständigen Pfad sowie Hinweise zum Funktions- und Contesttest. Die Datei ist selbst die dauerhafte Quelle; aus ihr abgeleitete Worked-Markierungen werden nicht in SQLite gespeichert und nicht automatisch für einen neuen Contest zurückgesetzt. @@ -862,7 +862,7 @@ Die interne SQLite-Datenbank speichert die contestbezogenen Zustände unabhängi - manuell gesetzte NOT-QRV-Tags pro Band und - gearbeitete vierstellige Großfelder pro Band. -Eine Ausnahme bilden Worked-Markierungen des Simplelogfile-Interpreters. Sie werden nur aus der ausgewählten Datei in den laufenden Zustand übernommen und nicht in SQLite persistiert. Die Datei ist die dauerhafte Quelle und besitzt keinen automatischen Contest-Reset. +Eine Ausnahme bilden Worked-Markierungen des Simplelogfile-Interpreters. Sie werden nur aus der ausgewählten Datei in den laufenden Zustand übernommen und nicht in SQLite persistiert. Die Datei ist die dauerhafte Quelle und besitzt keinen automatischen Contest-Reset. Ein Datenbank-Reset verändert oder leert sie nicht; enthaltene Rufzeichen werden bei der nächsten periodischen Auswertung erneut als gearbeitet markiert. Als Schlüssel wird das normalisierte Rufzeichen ohne sichtbare Chat-Klammern oder Kategorieformatierung verwendet. Dadurch können aktive Varianten desselben Rufzeichens konsistent ausgewertet werden. diff --git a/github_docs/de-Log-Synchronisation.md b/github_docs/de-Log-Synchronisation.md index 5f9ff70a..e01ce46d 100644 --- a/github_docs/de-Log-Synchronisation.md +++ b/github_docs/de-Log-Synchronisation.md @@ -18,7 +18,7 @@ Die Grenze ist ebenso eindeutig: Aus einem reinen Rufzeichentreffer lassen sich Den Pfad der Textdatei im Reiter **Log sync** auswählen. Fehlt die Datei, legt KST4Contest sie an und zeigt einmalig einen nicht blockierenden Hinweis mit dem Pfad und den nächsten Prüfschritten an. Lese- oder Erstellungsfehler werden protokolliert; die minütliche Auswertung läuft beim nächsten Termin weiter. Für bandbezogene Auswertungen sollte nach Möglichkeit eine der Netzwerkschnittstellen verwendet werden. -Der aus dem Simplelogfile abgeleitete Worked-Status wird nicht in der internen SQLite-Datenbank gespeichert. Die ausgewählte Datei ist die dauerhafte Quelle und wird auch nach einem Neustart erneut eingelesen. Der Interpreter setzt nur positive Worked-Markierungen; er entfernt während der laufenden Programmsitzung keine bereits gesetzte Markierung und führt beim Wechsel zu einem neuen Contest keinen automatischen Reset durch. Vor jedem Contest sollte deshalb geprüft werden, ob das Logprogramm genau die aktuelle Contestdatei beschreibt. +Der aus dem Simplelogfile abgeleitete Worked-Status wird nicht in der internen SQLite-Datenbank gespeichert. Die ausgewählte Datei ist die dauerhafte Quelle und wird auch nach einem Neustart erneut eingelesen. Der Interpreter setzt nur positive Worked-Markierungen; er entfernt während der laufenden Programmsitzung keine bereits gesetzte Markierung und führt beim Wechsel zu einem neuen Contest keinen automatischen Reset durch. Auch ein manueller Datenbank-Reset ändert oder leert das Simplelogfile nicht. Darin enthaltene Rufzeichen werden bei der nächsten Auswertung innerhalb einer Minute erneut als gearbeitet markiert. Vor jedem Contest sollte deshalb geprüft werden, ob das Logprogramm genau die aktuelle Contestdatei beschreibt. --- @@ -203,6 +203,6 @@ Die Datenquellen liefern unterschiedlich genaue Informationen: | QSO-UDP-Listener | ja | ja, wenn im Paket enthalten | ja, wenn Band und Locator enthalten sind | | Win-Test-Netzwerk-Listener | ja | ja | ja, wenn ein Locator enthalten ist | -Die in SQLite gespeicherten Daten werden beim Programmstart wieder geladen und bei neuen Logeinträgen während des Betriebs aktualisiert. Sie laufen nach drei Tagen automatisch ab. Ein Reset vor jedem Contest ist daher normalerweise nicht erforderlich. Für den Simplelogfile-Interpreter gilt diese Lebensdauer nicht: Seine Datei bleibt die dauerhafte Quelle und wird nicht automatisch auf einen neuen Contest zurückgesetzt. +Die in SQLite gespeicherten Daten werden beim Programmstart wieder geladen und bei neuen Logeinträgen während des Betriebs aktualisiert. Sie laufen nach drei Tagen automatisch ab. Ein Reset vor jedem Contest ist daher normalerweise nicht erforderlich. Für den Simplelogfile-Interpreter gilt diese Lebensdauer nicht: Seine Datei bleibt die dauerhafte Quelle und wird durch einen Datenbank-Reset weder geändert noch geleert. Enthaltene Rufzeichen setzt die nächste periodische Auswertung erneut auf den globalen Worked-Status. Ein vollständiger manueller Reset entfernt Worked-Markierungen, NOT-QRV-Tags und Worked-Großfelder gemeinsam. Weitere Einzelheiten: [Worked Station Database Settings](de-Konfiguration#worked-station-database-settings-gearbeitete-stationen-datenbank). diff --git a/github_docs/en-AirScout-Integration.md b/github_docs/en-AirScout-Integration.md index cd59bb5b..db685f68 100644 --- a/github_docs/en-AirScout-Integration.md +++ b/github_docs/en-AirScout-Integration.md @@ -2,7 +2,7 @@ > 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-AirScout-Integration) -AirScout (by DL2ALF) is a program for detecting aircraft for aircraft scatter operation. KST4Contest is tightly integrated with AirScout and shows reflectable aircraft directly in the user list. +AirScout (by DL2ALF) calculates aircraft-scatter opportunities from current aircraft positions. KST4Contest receives these results and displays aircraft suitable for the path to each remote station directly in the user list. > **Aircraft Scatter** enables very long-distance communication on VHF and higher – even for stations with low altitude above sea level or unfavourable topographic conditions. @@ -15,9 +15,9 @@ Download AirScout from: --- -## Aircraft Data Feeds (ADSB) +## Aircraft Data Feeds (ADS-B) -Public aircraft data feeds on the internet are often unreliable and limited in use. A recommended alternative is the dedicated ADSB feed service provided by **OV3T (Thomas)**: +Public aircraft data feeds on the internet are often unreliable and of limited use. A recommended alternative is the dedicated ADS-B feed service provided by **OV3T (Thomas)**: - https://airscatter.dk/ - https://www.facebook.com/groups/825093981868542 @@ -28,7 +28,7 @@ An account is required for this service. Please consider donating to Thomas – ## Setting Up AirScout -### Step 1: Configure the ADSB Feed in AirScout +### Step 1: Configure the ADS-B Feed in AirScout 1. Start AirScout. 2. Enter your OV3T feed account details (username, password, URL) in the AirScout settings. @@ -85,32 +85,40 @@ Otherwise, it may result in incorrect AP data. ## AP Column in the User List -After setup, an **AP column** appears in the user list showing up to two reflectable aircraft per station. +After setup, an **AP column** appears in the user list. For each station, it shows the arrival time and the AirScout reflection potential of the first two suitable aircraft. Example display: | Station | AP Info | |---|---| -| DF9QX | 2 Planes: 0 min / 0 min, 100% each | -| F5DYD | 2 Planes: 14 min / 31 min, 50% each | +| DF9QX | 0 (100%) / 0 (100%) | +| F5DYD | 14 (50%) / 31 (50%) | + +The number before the brackets is the number of minutes remaining until the calculated opportunity. The percentage is the reflection potential reported by AirScout. It is not a QSO probability. AP information is also available in the **private messages window**. -The percentage indicates the reflection potential (aircraft size, altitude, distance). +## Effect on the Priority Score and Timeline + +At least one aircraft reported as reachable by AirScout raises the station's Priority Score. An opportunity expected in zero, one or two minutes receives additional time-dependent weighting. AirScout is only one factor alongside Worked status, available bands, QRB, antenna direction, chat activity and skeds. + +The AP and sked timeline uses the Priority Score to select interesting stations and places the next suitable aircraft-scatter opportunity on the time axis. The reflection potential also controls how the AP marker is displayed. The timeline remains a preview and does not guarantee a QSO. --- ## AP Variables in Messages -Aircraft data can be inserted directly into messages: +Aircraft data for the selected station can be inserted directly into shortcuts, snippets and other station-specific messages: - `FIRSTAP` → e.g. `a very big AP in 1 min` - `SECONDAP` → e.g. `Next big AP in 9 min` Details: [Macros and Variables](en-Macros-and-Variables#variables) +Because these values require a selected remote station, `FIRSTAP` and `SECONDAP` are not available as global beacon variables. + --- ## "Show Path in AirScout" Button -In the user list there is a button with an arrow showing the direction (QTF) to the selected station. Clicking it maximises AirScout and shows the path with reflectable aircraft to the selected contact. +In the user list there is a button with an arrow showing the direction (QTF) to the selected station. Clicking it maximises the external AirScout window and displays the path to the selected remote station together with the calculated aircraft-scatter opportunities. The button does not start a separate terrain or propagation calculation in KST4Contest. diff --git a/github_docs/en-Changelog.md b/github_docs/en-Changelog.md index 7bf50dc8..a35b8a34 100644 --- a/github_docs/en-Changelog.md +++ b/github_docs/en-Changelog.md @@ -34,6 +34,8 @@ v1.42 brings several previously separate calculations together. Band information - **Manual QTF input:** The current antenna direction can be changed directly in KST4Contest when PSTRotator is not being used. +- **`MYQTF` message variable:** The current antenna direction can be inserted as a numeric angle in degrees into shortcuts, snippets and other supported message texts. + - **Filter reset:** A dedicated reset button reliably removes the active user-list filter predicates. - **Map clustering:** Stations close to each other are grouped at lower zoom levels. The selected station and relevant direction opportunities remain individually visible. @@ -80,7 +82,7 @@ v1.42 brings several previously separate calculations together. Band information - **DXLog full-log import:** In addition to `contactinfo`, the UCXLog-compatible UDP listener processes `contactreplace`. This allows a complete log broadcast by DXLog.net to be imported. -- **Defined Simplelogfile behaviour:** The selected text file is evaluated once per minute using a fixed callsign pattern. Matches set the global Worked status for all active variants of the base callsign but are not persisted in SQLite. A missing file is created, and read or creation errors do not terminate the periodic task. +- **Defined Simplelogfile behaviour:** The selected text file is evaluated once per minute using a fixed callsign pattern. Matches set the global Worked status for all active variants of the base callsign but are not persisted in SQLite. A missing file is created, and read or creation errors do not terminate the periodic task. A database reset does not change the file, so callsigns contained in it are marked as worked again during the next evaluation. - **Guarded automatic QRG updates:** `MYQRG` is updated only by an enabled interface which actually supplies valid `RadioInfo` or Win-Test `STATUS` packets. An enabled source which provides no data does not remove the need for a functional check or manual QRG maintenance. @@ -414,7 +416,6 @@ First publicly released version. Core features: ## Planned Features -- `MYQTF` variable (own antenna direction as text) - ~~Lifetime for worked status (automatic reset)~~ ✅ **Implemented in v1.40** (3-day lifetime, no manual reset needed anymore) - Filtering the "Cluster & QSO of others" window to own QTF - Further topography-based calculations for direction warnings diff --git a/github_docs/en-Configuration.md b/github_docs/en-Configuration.md index e302a29a..8bb9f4d2 100644 --- a/github_docs/en-Configuration.md +++ b/github_docs/en-Configuration.md @@ -136,7 +136,7 @@ The general QSO UDP listener is the recommended interface for UCXLog, QARTest, N Win-Test uses its own network protocol and therefore has a separate listener. Its default port is `9871`. If this port is changed while the listener is enabled, KST4Contest restarts the Win-Test listener on the new port. After changing the shared UDP port `12060`, KST4Contest must instead be restarted completely. -All enabled input paths may be used in parallel and identical reports do not create separate Worked states. Network-derived Worked information is stored in the internal database. Simplelogfile marks remain runtime state derived from the selected file. KST4Contest must be running when a network QSO is transmitted unless the logging application can resend the existing log. +All enabled input paths may be used in parallel and identical reports do not create separate Worked states. Network-derived Worked information is stored in the internal database. Simplelogfile marks remain runtime state derived from the selected file. Before using Simplelogfile, check whether the logging application already provides one of the supported network interfaces. KST4Contest must be running when a network QSO is transmitted unless the logging application can resend the existing log. Configuration of the individual logging applications, band and locator handling, and the Win-Test sked handover are described under [Log Synchronisation](en-Log-Sync). @@ -919,7 +919,7 @@ The internal SQLite database stores contest-related state independently of the l - manually assigned NOT-QRV marks per band, and - worked four-character grid squares per band. -Worked marks from the Simplelogfile interpreter are the exception. They are copied from the selected file into runtime state only and are not persisted in SQLite. The file is the durable source and has no automatic contest reset. +Worked marks from the Simplelogfile interpreter are the exception. They are copied from the selected file into runtime state only and are not persisted in SQLite. The file is the durable source and has no automatic contest reset. A database reset does not change or empty it; callsigns contained in the file are marked as worked again during the next periodic evaluation. The normalised callsign, without visible chat brackets or category formatting, is used as the key. This allows active variants of the same callsign to be evaluated consistently. diff --git a/github_docs/en-Features.md b/github_docs/en-Features.md index 443c336f..4e50248a 100644 --- a/github_docs/en-Features.md +++ b/github_docs/en-Features.md @@ -208,7 +208,7 @@ In plain terms: an automatically detected hint means "probably active on this ba Worked, NOT-QRV and worked-grid information received from network interfaces, together with manual marks, is stored in the internal SQLite database and restored on the next start. Entries expire automatically after three days, so a reset before every contest is normally unnecessary. -Simplelogfile matches are excluded. They are not persisted in SQLite but are derived from the selected file during each application session. The file is therefore the durable source. The interpreter does not remove an existing Worked mark during the current session and does not reset the state automatically for a new contest. +Simplelogfile matches are excluded. They are not persisted in SQLite but are derived from the selected file during each application session. The file is therefore the durable source. The interpreter does not remove an existing Worked mark during the current session and does not reset the state automatically for a new contest. A manual database reset does not change or empty the file. Callsigns contained in it are marked as worked again when the file is next evaluated within one minute. A manual reset under **Workedstn database** removes all Worked marks, NOT-QRV marks and stored worked grid squares. The known callsign rows remain in the database. See [Worked Station Database Settings](en-Configuration#worked-station-database-settings) for details. diff --git a/github_docs/en-Log-Sync.md b/github_docs/en-Log-Sync.md index 4aca9cb3..c2d5af54 100644 --- a/github_docs/en-Log-Sync.md +++ b/github_docs/en-Log-Sync.md @@ -18,7 +18,7 @@ The limitation is equally clear. A callsign match alone provides neither a relia Select the text-file path in the **Log sync** tab. If the file is missing, KST4Contest creates it and displays a one-time, non-blocking notice with the path and the checks to perform next. Read or creation errors are logged; the scheduled task continues with its next one-minute pass. Use one of the network interfaces where possible if band-specific information is required. -Worked status derived from the Simplelogfile is not stored in the internal SQLite database. The selected file is the durable source and is read again after every restart. The interpreter only adds positive Worked marks; it does not remove an existing mark during the current application session and does not reset automatically for a new contest. Before each contest, verify that the logging application is writing the current contest log to this exact file. +Worked status derived from the Simplelogfile is not stored in the internal SQLite database. The selected file is the durable source and is read again after every restart. The interpreter only adds positive Worked marks; it does not remove an existing mark during the current application session and does not reset automatically for a new contest. A manual database reset does not change or empty the Simplelogfile either. Callsigns contained in it are marked as worked again when the file is next evaluated within one minute. Before each contest, verify that the logging application is writing the current contest log to this exact file. --- @@ -204,6 +204,6 @@ The input sources provide different levels of detail: | QSO UDP listener | yes | yes, if included in the packet | yes, if both band and locator are available | | Win-Test network listener | yes | yes | yes, if a locator is available | -The information stored in SQLite is restored when KST4Contest starts and updated during operation when new log entries arrive. It expires automatically after three days, so a reset before every contest is normally unnecessary. This lifetime does not apply to the Simplelogfile interpreter: its file remains the durable source and is not reset automatically for a new contest. +The information stored in SQLite is restored when KST4Contest starts and updated during operation when new log entries arrive. It expires automatically after three days, so a reset before every contest is normally unnecessary. This lifetime does not apply to the Simplelogfile interpreter: its file remains the durable source and is neither changed nor emptied by a database reset. Callsigns contained in it set the global Worked status again during the next periodic evaluation. A complete manual reset removes Worked marks, NOT-QRV marks and worked grid squares together. See [Worked Station Database Settings](en-Configuration#worked-station-database-settings) for details. diff --git a/src/main/java/kst4contest/controller/ReadUDPByWintestThread.java b/src/main/java/kst4contest/controller/ReadUDPByWintestThread.java index d7b50f14..e480a64e 100644 --- a/src/main/java/kst4contest/controller/ReadUDPByWintestThread.java +++ b/src/main/java/kst4contest/controller/ReadUDPByWintestThread.java @@ -370,9 +370,9 @@ public class ReadUDPByWintestThread extends Thread { /** * Resolves the project Band enum from Win-Test band IDs. * - *

Only bands that exist in the current Band enum are returned. 50/70 MHz are - * still represented as worked flags in ChatMember, but they are not part of the - * current Reachability/New-Locator band enum.

+ *

Only bands that exist in the current Band enum are returned. The existing + * 50 MHz and 70 MHz values are resolved in the same way as the other supported + * VHF, UHF and microwave bands.

* * @param bandId Win-Test band id from ADDQSO * @return matching Band or null diff --git a/src/main/java/kst4contest/view/Kst4ContestApplication.java b/src/main/java/kst4contest/view/Kst4ContestApplication.java index 33e87caf..021b8a0b 100644 --- a/src/main/java/kst4contest/view/Kst4ContestApplication.java +++ b/src/main/java/kst4contest/view/Kst4ContestApplication.java @@ -11377,6 +11377,8 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL confirmation.setContentText( "This removes all worked markings, manually assigned NOT-QRV tags " + "and stored worked-grid information. The operation cannot be undone.\n\n" + + "The selected Simplelogfile is not changed. Callsigns contained in it will be " + + "marked as worked again when the file is read within the next minute.\n\n" + "A reset before every contest is normally not required because these data " + "expire automatically after three days." ); @@ -11419,7 +11421,8 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL information.setContentText( affectedLines + " callsign database entries were updated. " - + "Worked-grid data were cleared as well." + + "Worked-grid data were cleared as well. The selected Simplelogfile was not changed; " + + "callsigns contained in it will be marked as worked again when the file is next read." ); information.show(); }); @@ -12140,7 +12143,10 @@ public class Kst4ContestApplication extends Application implements StatusUpdateL Label explanation = new Label( "File: " + filePath + "\n\n" - + "Configure your logging application to write its live log to this file. " + + "First check whether you need the Simplelogfile integration. If your logging " + + "application provides a supported network interface, use that interface for " + + "band and locator information.\n\n" + + "If you use Simplelogfile, configure your logging application to write its live log to this file. " + "Then log a test QSO and verify that the callsign is marked as worked " + "in KST4Contest within one minute.\n\n" + "Before each contest, verify that the logging application writes the current " diff --git a/src/main/java/kst4contest/view/map/OfflineDemImportService.java b/src/main/java/kst4contest/view/map/OfflineDemImportService.java index 7c886bba..e1463430 100644 --- a/src/main/java/kst4contest/view/map/OfflineDemImportService.java +++ b/src/main/java/kst4contest/view/map/OfflineDemImportService.java @@ -14,16 +14,17 @@ import java.util.Locale; /** * Small helper service for preparing and filling the local offline DEM directory. * - *

This is intentionally the first practical step before adding a real network - * downloader: + *

This service only prepares local data for a possible future offline terrain + * provider: *

* - *

The active terrain provider already scans the configured root directory - * recursively. Therefore it is sufficient to import valid Copernicus DGED - * GeoTIFF files into one dedicated folder tree.

+ *

Importing files does not activate an offline provider or change the terrain + * calculation chain. The active provider remains Open-Meteo with Copernicus GLO-90 + * data. Valid Copernicus GLO-30 DGED GeoTIFF files are only copied into the prepared + * directory tree.

*/ public final class OfflineDemImportService { @@ -229,4 +230,4 @@ public final class OfflineDemImportService { String message ) { } -} \ No newline at end of file +} diff --git a/website/src/_data/version-history.xml b/website/src/_data/version-history.xml index 2beccd40..7876b442 100644 --- a/website/src/_data/version-history.xml +++ b/website/src/_data/version-history.xml @@ -7,93 +7,93 @@ 2026-07-01 Map view and path calculations -Band and Frequency Detection per Chatmember, Band alert, Win-Test SKED Push via UDP, -Win-Test Broadcast Defaults and SKed Workflow, Chat History at Startup, Station Map / Map View -Local Leaflet /-TileProxy Backend, Maidenhead /-Grid Overlay, Path calculation, path profile, -Reachability filters, NAC filters (grid sqaure marking) +Band and frequency detection per chat member, band alert, Win-Test sked push via UDP, +Win-Test broadcast defaults and sked workflow, chat history at startup, station map / map view, +local Leaflet / tile-proxy backend, Maidenhead / grid overlay, path calculation, path profile, +reachability filters, NAC filters (grid-square marking) -button housing, it works now on smaller screens / plus: detecting maximum screen size +Button layout now works on smaller screens; the maximum screen size is also detected -9A2HM reported that 23cm qsos with N1MM are not marked correctly, ist fixed +9A2HM reported that 23 cm QSOs with N1MM were not marked correctly; this is fixed 1.40 2026-02-16 - Much changes and fixes + Many changes and fixes -- win-test support (not deactivable yet, beta) -- QSO sniffer which filters changable callsigns lists messages to your pm window -- Chatmember Score system. Each chatmember gets a score depending to antenna direction, activity time, - activity msgcount, positive signals, active bands, active frequencies, his sked direction (degrees), - self handed rate, sked-made-rate and some others -- Chatmember Band and frequency recognition: now we list all active bands of each other chatmember +- Win-Test support (cannot be disabled yet, beta) +- QSO sniffer which filters messages from configurable callsign lists into the private-message window +- Chat-member score system. Each chat member receives a score based on antenna direction, activity time, + activity message count, positive signals, active bands, active frequencies, sked direction (degrees), + self-handed rate, sked-made rate and other factors +- Chat-member band and frequency recognition: all active bands of each other chat member are now listed - Band alert for logged stations -- Sked reminder ALERT with automatic messages in 2+1 / 5+2+1 / 10+5+2+1 minutes +- Sked reminder alert with automatic messages at 2+1 / 5+2+1 / 10+5+2+1 minutes - PSTRotator interface -- AirPlane Timeline -- Skedfail button in furtherinfo panel -- Wintest logsynch interface can now be activated and deactivated in the preferences -- load chat history on startup +- Airplane timeline +- Sked-fail button in the further-information panel +- Win-Test log-synchronisation interface can now be enabled and disabled in Preferences +- Load chat history at startup -- added save option: ServerDNS / Port -- added save option: activate/deactivate pstRotator interface -- added save option: activate/deactivate wintest interface -- added save option: callsign sniffer -- added save option: boolean GUI_darkModeActiveByDefault = false -- added AP notes at the internal DX cluster spots -- Generic Autoanswer fires maximum once in 45 seconds per rx callsign +- Added saved options for server DNS and port +- Added saved option to enable or disable the PSTRotator interface +- Added saved option to enable or disable the Win-Test interface +- Added saved option for the callsign sniffer +- Added saved option: boolean GUI_darkModeActiveByDefault = false +- Added AP notes to internal DX cluster spots +- Generic auto-answer fires at most once every 45 seconds per receiving callsign -- Userlist sort automatically on new member signon -- Posonpill-messages now kills only exactly one Client instance (bugreport 9A2HM) -- Crash of wtkst by disconnection of kst4Contest -- wtKST crashes when kst4contest is running (many reporters) -- wintest: logged per band excludes pre worked band (bugreport SM6VTZ) -- PSTRotator SOCKET Close on DISCONNECT BUTTON works now -- AirScout Map had not been updated (bugreport SM0RJV) -- QTFDefault had been not saved correctly (bugreport SM0RJV) -- Show path in AS button worked only with fixed server Strings (bugreport 9A2HM) -- Version number had been displayed wrong -- suffixes like /p, -2, etc. problem now fixed everywhere -- Dark mode: passing for qrg fields fix +- User list is sorted automatically when a new member signs on +- Poison-pill messages now terminate exactly one client instance (bug report 9A2HM) +- wtKST crash when KST4Contest disconnects +- wtKST crash while KST4Contest is running (many reporters) +- Win-Test: logging per band excludes previously worked bands (bug report SM6VTZ) +- The PSTRotator socket now closes when the disconnect button is used +- The AirScout map was not updated (bug report SM0RJV) +- QTFDefault was not saved correctly (bug report SM0RJV) +- The Show Path in AirScout button worked only with fixed server strings (bug report 9A2HM) +- The version number was displayed incorrectly +- Problems with suffixes such as /P and -2 are now fixed throughout the application +- Dark mode: padding of QRG fields fixed -- No more date display. Not needed. Saving space, only time is important +- Date display removed to save space; only the time is relevant 1.31 2025-12-13 - Much changes and a hotfix + Many changes and a hotfix -- win-test support (not deactivable yet, beta) -- pstRotator support (not deactivable yet, beta) -- airScout fix (calculations depends to cpu load now) +- Win-Test support (cannot be disabled yet, beta) +- PSTRotator support (cannot be disabled yet, beta) +- AirScout fix (calculations now depend on CPU load) - QSO sniffer - DNS from www.on4kst.info to www.on4kst.org (hotfix, now configurable in preferences) -- Endless loop in error case lets freeze the client -- PSTRotator SOCKET Close on DISCONNECT BUTTON -- Dark mode: passing for qrg fields fix +- An endless loop in an error case froze the client +- PSTRotator socket closes when the disconnect button is used +- Dark mode: padding of QRG fields fixed 1.266 2025-10-03 - Airscout interface did not work with multi-signons + AirScout interface did not work with multiple sign-ons nothing nothing -Fixed by using raw callsign (without -2 suffix etc.) when communicating with AirScout. +Fixed by using the raw callsign (without a -2 suffix, etc.) when communicating with AirScout. Thank you very much for testing this, Kreso 9A2HM! @@ -101,36 +101,36 @@ Thank you very much for testing this, Kreso 9A2HM! 1.265 2025-09-28 - Direction buttons stay now colored, if activated + Direction buttons now stay coloured when activated nothing nothing - The buttons stay now colored, if activated + The buttons now stay coloured when activated 1.264 2025-08-02 - Changed the callsign recognition pattern for Simplelogfile + Changed the callsign-recognition pattern for Simplelogfile nothing nothing -Callsigns like S53CC, S51A etc. are now correctly marked as worked in SimpleLogFile.txt. -(bugreport Boris, S53CC) +Callsigns such as S53CC and S51A are now correctly marked as worked in SimpleLogFile.txt. +(bug report by Boris, S53CC) 1.263 2025-06-08 - Airscout communication and Loginname + AirScout communication and login name nothing -Only entries with QRB lower than max-QRB are sent to AirScout in 60s intervals (was 12s for all). +Only entries with a QRB below the maximum QRB are sent to AirScout at 60-second intervals (previously 12 seconds for all entries). -- AS communication message count hugely reduced -- Name in chat is now saveable -- Fixed AS client name (was hard-wired to "KST") +- AirScout communication message count greatly reduced +- Name in chat can now be saved +- AirScout client name fixed (was hard-coded as "KST") 73 / DO5AMF @@ -138,39 +138,39 @@ Only entries with QRB lower than max-QRB are sent to AirScout in 60s intervals ( 1.262 2025-05-21 - Freezes caused by getting messages before user login should be fixed now + Freezes caused by receiving messages before user login should now be fixed nothing nothing -ON4KST delivers messages of stations not yet logged in. That caused a freeze at the message -processing engine which is now fixed. +ON4KST delivers messages from stations which are not yet logged in. This caused the message-processing +engine to freeze and is now fixed. 1.26 2025-05 - Login to multiple Channels via single signon / spend some colors + Login to multiple channels via single sign-on / added some colour -1. UI: Dark mode. Switch in "Window -> use dark mode" -2. Usage of two Chatcategories at the same time -3. opposite station multi-callsign login-tagging +1. UI: Dark mode. Switch under "Window -> use dark mode" +2. Use of two chat categories at the same time +3. Multi-callsign login tagging for remote stations 73 / DO5AMF -- Coloring mechanic of the software. Modify colors via css by yourself... +- Colour handling in the application. Colours can be modified through CSS. -- Station tagging fixed completely +- Station tagging completely fixed 1.251 2025-02 - BUGFIX of 1.25, tnx Steve Clements! + Bug fix for 1.25, thanks to Steve Clements! -- Steve spotted a problem in udp broadcast spot info reading, its now fixed! +- Steve found a problem when reading UDP broadcast spot information; it is now fixed. 73 / DO5AMF @@ -182,13 +182,13 @@ processing engine which is now fixed. 2025-02 Wishlist-time -- New configuration Tab: Messagehandling (auto-answering, CQ qrg auto-answer) -- Coloured lines: new pm rows appear in red, fade rainbow-like to white over 30s (tnx Gianluca) +- New configuration tab: Message handling (automatic replies, CQ QRG automatic reply) +- Coloured lines: new private-message rows appear in red and fade through a rainbow to white over 30 seconds (thanks to Gianluca) 73 / DO5AMF -- Users with suffixes like "-2 and -70" are now correctly marked as worked +- Users with suffixes such as -2 and -70 are now correctly marked as worked @@ -197,8 +197,8 @@ processing engine which is now fixed. 2024-11 Wishlist-time -- Button to show qrz.com profile of a selected station -- Button to show qrzcq.com profile of a selected station +- Button to show the qrz.com profile of a selected station +- Button to show the qrzcq.com profile of a selected station @@ -207,10 +207,10 @@ processing engine which is now fixed. 1.23 2024-10 - DXCluster Server is now implemented + DX cluster server is now implemented -- DXCluster Server (tnx OMAAO): KST4Contest now provides a DXCluster server to feed - your log client with station-reachable warnings. +- DX cluster server (thanks to OMAAO): KST4Contest now provides a DX cluster server which sends + reachable-station warnings to the logging client. @@ -219,13 +219,13 @@ processing engine which is now fixed. 1.22 2024-05 - Increase usability, fixed AS button + Improved usability and fixed AirScout button - Variables (tnx OMAAO): MYLOCATORSHORT, MYQRGSHORT, QRZNAME - - Sendtext-field focus on callsign click + - Message-input focus when clicking a callsign -- Worked-station-filter (tnx Gianluca): filter is now live -- Chatters list sorting by QRB (tnx Alessandro): fixed to numeric sort -- Airscout showpath button now maximizes AS and shows the path +- Worked-station filter (thanks to Gianluca): the filter is now live +- User-list sorting by QRB (thanks to Alessandro): changed to numeric sorting +- AirScout Show Path button now maximises AirScout and displays the path @@ -235,8 +235,8 @@ processing engine which is now fixed. Increase usability -- Window sizes and divider positions are now stored and restored on next startup -- Filters section is now a flowpane for lower resolutions +- Window sizes and divider positions are now stored and restored at the next startup +- The filters section now uses a FlowPane for lower resolutions @@ -248,7 +248,7 @@ processing engine which is now fixed. - Selectable bands - Unworkable tags for each callsign per band -- QTF-Arrow on the "show path in AS" button +- QTF arrow on the "Show Path in AirScout" button @@ -259,15 +259,15 @@ processing engine which is now fixed. 2024-03 Increased workflow -- Reachable warning function +- Reachable-station warning function - Variables FIRSTAP and SECONDAP for predefined texts - Marking new connected stations (bold) and away-state (brackets) -- Activity-timer since last message of a chatter +- Activity timer since a user's last message - - QRB/QTF info in pm-window + - QRB/QTF information in the private-message window -- Behaviour of messagefilter-radiobutton corrected (tnx Gian) -- Error sending macros on selected stations in pm window (tnx Gian) +- Behaviour of the message-filter radio button corrected (thanks to Gian) +- Error when sending macros to selected stations in the private-message window fixed (thanks to Gian) - boot sound @@ -276,13 +276,13 @@ processing engine which is now fixed. 2024-02 First stable release -- audio notification support -- update-available warning -- changelog displaying -- known-bugs displaying -- message filters for selected station -- stationlist-filters (show by qtf / textstring, hide by qrb, qtf, workedstate) -- 10 macros (textsnippets available by hitting strg+numberkey) +- Audio-notification support +- Update-available warning +- Changelog display +- Known-bugs display +- Message filters for the selected station +- Station-list filters (show by QTF / text string; hide by QRB, QTF or Worked state) +- 10 macros (text snippets available with Ctrl+number key) @@ -291,27 +291,27 @@ processing engine which is now fixed. 0.9 2024-02 - Now the chat is disconnectable without closing it + The chat can now be disconnected without closing the application - disconnect-button, Textsnippets in CQ Window, "/CQ" at click on own sendtexts, -setname "qrg" works now + Disconnect button, text snippets in the CQ window, "/CQ" when clicking own sent texts; +setname "qrg" now works 0.8 2023-10 - savesettings function and disconnect function added. MYCALL-Highlighting fixed - savesettings function, disconnect function + Save-settings and disconnect functions added. MYCALL highlighting fixed + Save-settings function, disconnect function - MYCALL-Highlighting + MYCALL highlighting 0.7 2023-07 - Internal database for worked stations, shortcut and textsnippet editor - database, shortcut-editor, textsnipped-editor + Internal database for worked stations, shortcut editor and text-snippet editor + Database, shortcut editor, text-snippet editor @@ -319,8 +319,8 @@ setname "qrg" works now 0.6 2023-07 - Added periodically sent beacon function - beacon to public channel + Added a periodically sent beacon function + Beacon to the public channel @@ -328,8 +328,8 @@ setname "qrg" works now 0.5 2023-02 - Airscout interface, UDP interfaces for worked-station data and TRX info, shortcuts - Airscout-interface, packetreceiver for ucxlog, n1mm, qartest + AirScout interface, UDP interfaces for Worked-station data and TRX information, shortcuts + AirScout interface, packet receivers for UCXLog, N1MM and QARTest @@ -337,8 +337,8 @@ setname "qrg" works now 0.4 2022-12 - Worked info by logfile via universal pattern matching logfile interpreter - simple-logfile + Worked information from a log file through a universal pattern-matching log-file interpreter + Simplelogfile @@ -346,7 +346,7 @@ setname "qrg" works now 0.3 2022-10 - Added a GUI, chat was text based only + Added a GUI; the chat had previously been text-based only Graphical user interface @@ -355,8 +355,8 @@ setname "qrg" works now 0.2 2022-10 - Pattern matching system for frequency information, frequency collection per chatmember - frequency-extraction for every callsign + Pattern-matching system for frequency information, frequency collection per chat member + Frequency extraction for every callsign @@ -364,7 +364,7 @@ setname "qrg" works now 0.15 2022-09 - Researched the Chatprotocol and developed the base communication with the chatserver + Researched the chat protocol and developed the basic communication with the chat server diff --git a/website/src/features/log-sync.md b/website/src/features/log-sync.md index 463cbe22..eae077b5 100644 --- a/website/src/features/log-sync.md +++ b/website/src/features/log-sync.md @@ -39,7 +39,7 @@ The available information depends on the interface: The Simplelogfile interpreter reads the selected text file once per minute using a fixed callsign pattern. Matches are normalised to the base callsign and set the global Worked status for all active variants. A callsign match does not provide enough information to infer a reliable band or grid square. -If the file does not exist, KST4Contest creates it and displays the path together with the initial setup and contest checks. The file itself is the durable source. Its Worked marks are not stored in SQLite, are not removed automatically during the running session and are not reset automatically for a new contest. +If the file does not exist, KST4Contest creates it and first asks you to check whether Simplelogfile is needed or whether the logging application provides a supported network interface. The notice then displays the path together with the initial setup and contest checks. The file itself is the durable source. Its Worked marks are not stored in SQLite, are not removed automatically during the running session and are not reset automatically for a new contest. The general UDP listener processes packets from UCXLog, N1MM+, QARTest and DXLog.net. Where the packet contains band and locator data, KST4Contest also updates the per-band Worked state and worked grid square. @@ -59,7 +59,7 @@ Win-Test can additionally receive skeds created in KST4Contest. The handover onl Worked, NOT-QRV and worked-grid information received through the network interfaces, together with manual marks, is stored in the internal SQLite database and restored after a restart. Contest-related records expire automatically after three days. -Simplelogfile marks follow a different data flow: they remain runtime state derived from the selected file. The file is read again after a restart and has no automatic contest reset. +Simplelogfile marks follow a different data flow: they remain runtime state derived from the selected file. The file is read again after a restart and has no automatic contest reset. A database reset does not change or empty it. Callsigns contained in the file are marked as worked again during the next evaluation within one minute. KST4Contest can only use the fields supplied by the selected interface. Missing band or locator data is not reconstructed from guesswork. This makes the result less complete in some cases, but also avoids turning an incomplete log packet into incorrect Worked information. diff --git a/website/src/news/2026-07-08-hotfix-version-1-41-1.md b/website/src/news/2026-07-08-hotfix-version-1-41-1.md index 6a202306..f87b7ed7 100644 --- a/website/src/news/2026-07-08-hotfix-version-1-41-1.md +++ b/website/src/news/2026-07-08-hotfix-version-1-41-1.md @@ -1,9 +1,9 @@ --- title: Hotfix Version 1.41.1 -summary: Hotfix of a bug in Version 1.41 +summary: Hotfix for a bug in version 1.41 date: 2026-07-08 --- ## Version 1.41.1 -We had a bug, where KST4Contest would clear out the text field, where you would send your messages after a period. It also happend to set your Cursor back to the Sending Field, when you were filtering for a station. We fixed this bug today. The new release is [here](https://github.com/praktimarc/kst4contest/releases/tag/v1.41.1). You can also download the artifacts as always via the [Downloads-Page](/download/). +KST4Contest cleared the message input field after a while. It could also move the cursor back to that field while you were filtering for a station. This bug is fixed in version 1.41.1. The new release is available [here](https://github.com/praktimarc/kst4contest/releases/tag/v1.41.1). You can also download the artifacts as usual from the [downloads page](/download/).