updated english manuals for changes from 1.40 due to 1.42

github_docs/en-Configuration.md

@@ -25,7 +25,18 @@ Enter your own callsign and Maidenhead locator (6 characters, e.g., `JN49IJ`). T
 
 ### Active Bands
 
-Use the **"my station uses band"** checkboxes to select the active bands. Buttons and table rows will only appear in the user interface for selected bands. The software must be restarted after making changes.
+The **My station uses …** checkboxes define the bands available in the current local station setup. Supported choices are 50 MHz, 70 MHz, 144 MHz, 432 MHz, 1296 MHz, 2320 MHz, 3400 MHz, 5760 MHz and 10 GHz.
+
+This selection controls more than the visible band columns. It is also used for:
+
+- the per-band Worked and NOT-QRV filters,
+- the NOT-QRV controls visible in the **Further Info** panel,
+- the `a` and `B+` band-opportunity calculation,
+- the **New bands** filter,
+- the band-upgrade hint after a log entry, and
+- band-specific priority and Reachability functions.
+
+After a change, click **Save Settings** and restart KST4Contest. Band columns and several related controls are created while the user interface is being built and are therefore not added or removed completely during the current session.
 
 ### Antenna Beamwidth
 
@@ -87,12 +98,64 @@ Configuration of the interface to AirScout for aircraft scatter detection. Detai
 
 ## Notification Settings
 
+![Notifications, DX cluster output and QSO monitoring](client_settings_window_notification.png)
+
 Three notification types are available:
 
 1. **Simple sounds**: TADA sound for incoming messages, tick for sked direction detection, etc.
 2. **CW announcement**: The callsign of a station sending a private message is output as a CW signal.
 3. **Phonetic announcement**: The callsign is pronounced phonetically.
 
+### Fallback Band for Relative QRG Detection
+
+The **Fallback band for relative QRG detection** dropdown selects the band used when a relative QRG cannot be assigned to a recent station-specific band context.
+
+Only band prefixes supported by the frequency parser are available:
+
+```text
+50 MHz
+70 MHz
+144 MHz
+432 MHz
+1296 MHz
+2320 MHz
+3400 MHz
+5760 MHz
+10368 MHz (10G)
+24048 MHz (24G)
+```
+
+The dropdown is neither a filter nor an override for complete frequencies. `432.088` is recognised as a frequency in the 432 MHz band regardless of the selection. The fallback is needed for relative values such as `.205`, `,205` or `qrg 205`.
+
+Before using the fallback, KST4Contest checks the sender's recent band context. If a complete frequency has been detected for the same station during the previous 30 minutes, that band takes precedence. A fallback setting of `144 MHz` therefore still turns `.100` into `432.100 MHz` if the station mentioned `432.088` shortly before.
+
+Although the setting is located in the Notification tab, it affects the general QRG parser. It therefore influences the QRG column, detected active bands, priority calculations, band-upgrade hints and other functions which use a known station frequency – not only DX cluster spots.
+
+### Band Upgrade Hint after a Log Entry
+
+After receiving a log entry from UCXLog or Win-Test, KST4Contest can check whether the station which has just been worked still offers another common and unworked band.
+
+The check uses the same derivation as the `a` and `B+` display:
+
+1. the bands enabled in the local station settings,
+2. QRGs detected for the remote station during the previous 30 minutes,
+3. explicit band designators in the name fields of its active chat entries,
+4. stored per-band Worked marks, and
+5. manually assigned NOT-QRV marks.
+
+Active chat variants of the same normalised callsign are evaluated together. NOT-QRV takes precedence over an automatically detected QRG or band designator.
+
+If at least one common and unworked band remains, the main window displays a blinking **BAND+** hint for approximately twelve seconds. The callsign and remaining bands are included in the button text; the tooltip contains the complete derivation. If general notification sounds are enabled, KST4Contest also plays a short sound.
+
+The two options serve different purposes:
+
+- **Blink + sound …** enables the hint after a matching log entry.
+- **Priority boost …** additionally raises the priority of stations with an open band opportunity. The boost is one factor within the complete score calculation and does not guarantee a particular list position.
+
+The hint requires a log-synchronisation source which provides band information. The file-based callsign interpreter sees callsigns only and cannot reliably identify the band of the QSO which has just been logged.
+
+Further explanation: [Band Upgrade Hint after a Log Entry](en-Features#band-upgrade-hint-after-a-log-entry).
+
 ---
 
 ## Shortcut Settings
@@ -174,14 +237,37 @@ Use case: Keep track of important stations (e.g. DX expeditions or trusted conte
 
 ---
 
+## GUI Settings: Band-Column Hints
+
+Two optional additions to the band columns can be enabled or disabled in the **GUI** tab:
+
+- **Show "o" in band columns …** displays an `o` if the four-character grid square has already been worked on the relevant band. Disabling the option does not delete any database records; it only hides the additional indicator in the band columns. `wkdany` is unaffected.
+- **Show "a" in band columns …** distinguishes a completely new callsign from a band opportunity involving a callsign already worked elsewhere. When disabled, both cases are displayed as `B+`. The band-opportunity calculation itself remains unchanged.
+
+Changes are reflected in the current user interface immediately. Click **Save Settings** afterwards if they should persist after the next start.
+
+![GUI settings for band-column hints](client_settings_window_gui.png)
+
+---
+
 ## Worked Station Database Settings
 
-The internal worked database contains:
+The internal SQLite database stores contest-related state independently of the logging application's database:
 
-- Worked status of all stations (per band)
+- the global Worked status of a callsign,
-- NOT-QRV tags (since v1.2)
+- Worked status per band,
+- manually assigned NOT-QRV marks per band, and
+- worked four-character grid squares per band.
 
-**From v1.40**: Entries have an automatic lifetime of **3 days** – manually resetting before each contest is no longer strictly necessary. For a full reset, the **"Reinitialize"** button is still available.
+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.
+
+Worked and NOT-QRV information expires automatically three days after its most recent change. Stored grid squares expire three days after the corresponding log entry. A manual reset before every contest is therefore normally unnecessary.
+
+The **Reset worked, NOT-QRV and grid data...** button removes every Worked mark, NOT-QRV mark and stored worked grid square. A confirmation dialog is displayed first. Known callsign rows remain in the database; only the contest-related state is reset.
+
+A reset is useful when you deliberately want to start with an empty contest state or have imported test data. It is not intended as a daily maintenance step.
+
+Display and derivation: [Worked Callsigns, New Bands and New Grid Squares](en-Features#worked-callsigns-new-bands-and-new-grid-squares).
 
 ---
 

github_docs/en-Features.md

@@ -48,26 +48,92 @@ Recognised formats: `144.205`, `432.088`, `.205` (with configured band assumptio
 
 ---
 
-## Worked Marking
+## Worked Callsigns, New Bands and New Grid Squares
 
-Worked stations are visually marked in the user list – per band. Based on [Log Synchronisation](en-Log-Sync) via UDP or Simplelogfile.
+KST4Contest distinguishes between three pieces of information which may look similar during a contest but answer different questions:
 
-Reset the database before each contest: [Configuration – Worked Station Database Settings](Configuration#worked-station-database-settings).
+1. Has this callsign been worked before?
+2. Has this callsign been worked on a particular band?
+3. Has the four-character Maidenhead grid square already been worked, possibly with a different station?
 
----
+This distinction matters. A callsign already worked on one band may still be useful on another. Conversely, a new callsign may be located in a grid square which is already in the log.
 
-## NOT-QRV Tags (from v1.2)
+### Worked information from the log
 
-When a station indicates it is not QRV on a specific band, this can be manually marked:
+[Log Synchronisation](en-Log-Sync) imports new QSOs from the logging application. The amount of information available depends on the interface being used:
+
+- The file-based Simplelogfile interpreter detects callsigns only. It can therefore set only the global Worked status.
+- The QSO UDP interfaces and the Win-Test network listener can also provide the band.
+- If the log packet contains a valid locator, KST4Contest additionally stores the worked four-character grid square for that band.
+
+Missing information is not guessed. A QSO without a locator does not create a worked-grid record, and a Simplelogfile match does not create a band-specific Worked mark.
+
+### Meaning of the band columns
+
+The shared **worked** column contains only the bands enabled under **Station → My station uses …**. Its cells deliberately use short status codes because a full description would leave very little room for the actual user list.
+
+| Display | Meaning |
+|---|---|
+| `X` | The callsign has been worked on this band. |
+| `a` | The station offers this band, the band has not been worked yet, and the callsign has not been worked on any band. |
+| `B+` | The station offers this band and it has not been worked yet. The callsign has already been worked on another band. If the separate `a` display is disabled, a completely new callsign is also shown as `B+`. |
+| `o` | The station's four-character grid square has already been worked on this band, regardless of callsign. |
+| empty | No matching information is available for this band. This does not mean that the station is not QRV. |
+
+The `o` is an independent overlay and can therefore be combined with the other codes. Examples include `Xo`, `ao` and `B+o`. A single `o` means that the grid square has been worked on this band, while the displayed callsign has neither a Worked mark nor a current band opportunity.
+
+![Band-specific Worked status and worked grid squares](worked_band_status.png)
+
+### How is a band opportunity derived?
+
+KST4Contest displays `a` or `B+` only if it can derive an open band opportunity. The calculation combines:
+
+1. the bands enabled for the local station,
+2. QRGs detected for the remote station during the previous 30 minutes,
+3. explicit band designators in the remote station's name field,
+4. stored per-band Worked marks, and
+5. manually assigned NOT-QRV marks.
+
+Active chat entries with the same normalised callsign are evaluated together. This is particularly relevant when the station appears in several chat categories or with different visible callsign variants. An explicit band designator in the name field remains useful while the corresponding chat entry is active. A band derived from a detected QRG expires after 30 minutes.
+
+The remaining set contains only bands which are enabled locally, known for the remote station and not yet worked. A manual NOT-QRV mark overrides automatically detected evidence. The chat category alone is not sufficient evidence that an individual station is QRV on a particular band.
+
+The global Worked mark does not decide whether a band opportunity exists. It merely selects `a` or `B+` for the display. The actual opportunity calculation uses per-band Worked information.
+
+### Meaning of `wkdany`
+
+The **wkdany** subcolumn combines the global callsign and grid-square status:
+
+| Display | Meaning |
+|---|---|
+| empty | Neither the callsign nor the four-character grid square has been worked. |
+| `x` | The callsign has been worked on at least one band. |
+| `o` | The four-character grid square has been worked on at least one band. |
+| `xo` | Both the callsign and the grid square have been worked. |
+
+`wkdany` is deliberately band-independent. The lower-case `x` must therefore not be confused with the upper-case `X` in a band column. The global status is used for the overview and the global **wkd** filter; it is not a substitute for per-band Worked information.
+
+### NOT-QRV marks
+
+If a station reports that it is not QRV on a particular band, mark this in the selected station's **Further Info** panel:
 
 1. Select the station in the user list.
-2. Right-click → Set NOT-QRV for the appropriate band.
+2. Enable the relevant band under **Not QRV**.
+3. Use **tag not qrv all** only if the station should not be requested on any supported band.
 
-These tags are stored in the internal database and persist after a KST4Contest restart. Can be reset via the settings.
+The individual NOT-QRV controls are shown for the bands enabled at the local station. **tag not qrv all**, however, marks every supported band, including bands which are not currently visible in the user interface. The state is stored per band under the normalised callsign and propagated to its active chat variants.
 
-**Benefit**: Prevents repeated sked requests on bands where the station is not active – saves time for both sides.
+![Per-band NOT-QRV marks in the Further Info panel](not_qrv_controls.png)
 
----
+NOT-QRV is a manual correction and therefore takes precedence over detected QRGs and band designators in the name field. The affected band is no longer offered as `a` or `B+`, is not counted as an opportunity by the **New bands** filter and is excluded by the corresponding band filter.
+
+In plain terms: an automatically detected hint means "probably active on this band". A manual NOT-QRV mark means "do not request this station on this band". The next detected number must not silently reverse that decision.
+
+### Storage and lifetime
+
+Worked, NOT-QRV and worked-grid information 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.
+
+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.
 
 ## Direction Filter
 
@@ -83,9 +149,19 @@ Hide stations beyond a maximum distance. The **"Show only QRB [km] <="** button
 
 ---
 
-## Worked and NOT-QRV Filter
+## Filters for Worked Status, New Bands and New Grid Squares
 
-Toggle buttons (one per band) to hide already-worked stations and/or NOT-QRV-tagged stations. The filter takes effect **immediately** without manually reactivating (live since v1.22).
+The filters above the user list use the same information as the Worked columns:
+
+- **wkd** hides callsigns which have been worked on at least one band.
+- The individual band buttons hide a station if the callsign has already been worked on that band or has manually been marked NOT QRV there.
+- **New bands** shows only stations for which at least one locally enabled and unworked band is known. It evaluates recent QRG detections and band designators in the name field; NOT-QRV takes precedence.
+- **Only new grids** shows only stations whose four-character grid square has not been worked on any band. Stations without a valid locator do not pass this filter.
+- **Grid color** does not filter the list. When enabled, it gives the QRA cell of an already worked grid square a slightly darker background. New grid squares retain the normal table colour.
+
+Several active filters are applied together. A station remains visible only if it satisfies every selected condition. The filters react immediately to new log entries and changed NOT-QRV marks.
+
+Operation and layout of the filter bar: [User Interface – Filters](en-User-Interface#filters).
 
 ---
 
@@ -177,15 +253,19 @@ Configuration: [Configuration – PSTRotator Settings](en-Configuration#pstrotat
 
 ---
 
-## Band Alert for New QSOs (from v1.40)
+## Band Upgrade Hint after a Log Entry
 
-When a station is logged, KST4Contest automatically checks whether that station has shown any other active bands in the chat that you are also QRV on. If so, a **hint alert** appears so no multi-band opportunity is missed.
+When UCXLog or Win-Test reports a new log entry with band information, KST4Contest checks whether the worked station still offers another common band.
 
----
+The calculation follows the same rules as `a`, `B+` and the **New bands** filter: locally enabled bands, recent QRG detections, band designators in the name field, per-band Worked marks and NOT-QRV marks. Active chat variants of the same normalised callsign are evaluated together.
 
-## Worked Tag Lifetime (from v1.40)
+If at least one common and unworked band remains, a blinking hint appears for approximately twelve seconds. It includes the callsign and the remaining bands, for example `BAND+ DL0ABC 432, 1296`. Its tooltip also lists the enabled, worked and NOT-QRV bands used for the decision. If general notification sounds are enabled, KST4Contest also plays a short sound.
 
-Worked stations are automatically removed from the database after **3 days**. Manually resetting the worked database before each contest is therefore no longer strictly necessary – the database keeps itself up to date.
+The Simplelogfile interpreter cannot trigger this hint reliably because it provides no band information for the QSO which has just been logged.
+
+Configuration: [Band Upgrade Hint after a Log Entry](en-Configuration#band-upgrade-hint-after-a-log-entry).
+
+Worked, NOT-QRV and worked-grid data expire automatically after three days. See [Worked Station Database Settings](en-Configuration#worked-station-database-settings) for the lifetime and manual reset behaviour.
 
 ---
 

github_docs/en-Log-Sync.md

@@ -2,7 +2,7 @@
 
 > 🇬🇧 You are reading the English version | 🇩🇪 [Deutsche Version](de-Log-Synchronisation)
 
-KST4Contest automatically marks worked stations in the chat user list. Two basic methods are available:
+KST4Contest imports worked stations from the logging application and derives the global Worked status, per-band Worked marks and – where a locator is available – worked grid squares. Three input paths are available: the file-based Simplelogfile interpreter, the general QSO UDP listener and the dedicated Win-Test network listener.
 
 ---
 
@@ -10,24 +10,25 @@ KST4Contest automatically marks worked stations in the chat user list. Two basic
 
 ## Method 1: Universal File Based Callsign Interpreter (Simplelogfile)
 
-KST4Contest reads a log file and searches for callsign patterns using a regular expression. Binary log files are also supported – unreadable binary content is simply ignored.
+KST4Contest reads a log file and searches it for callsigns using a configurable regular expression. The file is read only and is never modified. Binary log files can also be used; content which cannot be interpreted as text is skipped.
 
-**Advantage**: Works with almost any logging program that writes a file.
+The advantage is broad compatibility: no dedicated network interface is required from the logging application.
-**Disadvantage**: No band information available – stations are only marked as "worked", not on which band.
 
-Enter the path to the log file in the Preferences. The file is only read, never modified (read-only).
+The limitation is equally clear. A callsign match alone provides neither a reliable band nor a locator. The Simplelogfile interpreter can therefore set only the global Worked status. It does not create a per-band `X`, a worked-grid record or a reliable basis for the band-upgrade hint after a log entry.
 
-> **Tip**: The Simplelogfile function can also be used to mark stations that are definitely unreachable (e.g. personal notes). This will be replaced in a later version by a better tagging system.
+Configure the log-file path and regular expression in the **Log sync** tab. Use one of the network interfaces where possible if band-specific information is required.
 
 ---
 
-## Method 2: Network Listener (UDP Broadcast) – Recommended
+# Method 2: Network Listener for QSO UDP Packets – Recommended
 
-When saving a QSO, the logging software sends a UDP packet to the broadcast address of the home network. KST4Contest receives this packet and marks the station including **band information** in its internal SQLite database.
+UCXLog, QARTest, N1MM+ and DXLog.net can transmit a UDP packet when a QSO is saved. KST4Contest receives these packets on port `12060` by default and imports the callsign together with any band and locator information they contain.
 
-> **Important**: KST4Contest must be **running in parallel with the logging software**. QSOs logged while KST4Contest is not running will not be captured – except with QARTest (which can send the complete log).
+If a band is available, the callsign is marked as worked on that band. If the packet also contains a valid locator, KST4Contest stores its four-character grid square for that band. Missing information is not inferred from unrelated fields.
 
-**Default UDP port**: 12060 (matches the default of most logging programs)
+KST4Contest must be running when the packet is transmitted. Some logging applications can, however, resend an existing log: QARTest provides **Invia log completo**, while DXLog.net sends `contactreplace` packets when broadcasting the complete log. KST4Contest processes both mechanisms.
+
+**Default port:** `12060`
 
 ---
 
@@ -81,11 +82,16 @@ For the built-in DX cluster server: configure N1MM+ as a DX cluster client (serv
 - Enter the IP of the KST4Contest computer (green-highlighted fields)
 - Port: 12060
 
+When broadcasting the complete logbook, DXLog.net uses `contactreplace` instead of `contactinfo`. KST4Contest processes both packet types. Older QSOs can therefore be imported by starting a complete-log broadcast while KST4Contest is running.
+
 ### Win-Test
 
 Win-Test is supported with a dedicated UDP network listener that understands the native Win-Test network protocol.
 
+For a new QSO, KST4Contest imports the callsign and resolves the native Win-Test band ID. This includes 50 and 70 MHz. If the packet contains a valid locator, the worked grid square is also stored for the detected band.
+
 **Advantages of Win-Test Integration:**
+- **Per-band Worked data:** New QSOs set the Worked mark for the band reported by Win-Test and update the grid-square status where a locator is available.
 - Automatic QSO synchronization to mark worked stations.
 - **Sked Handover (ADDSKED):** Using the "Create sked" button in the station info panel not only creates a sked in KST4Contest but also *sends it directly via UDP to the Win-Test network as an ADDSKED packet* – automatically, as soon as the listener is active. No separate toggle is needed.
 - You can choose between "AUTO", "SSB", or "CW" sked modes.
@@ -144,6 +150,16 @@ For DM5M-style setups (2 radios, 2 computers, one KST4Contest instance or two se
 
 ## Internal Database
 
-KST4Contest stores worked information in an internal **SQLite database**. This is independent of the logging program's database and is only populated via the UDP broadcast.
+KST4Contest stores Worked, NOT-QRV and worked-grid information in its own SQLite database. This database is independent of the logging application's database.
 
-Before each new contest: reset the database! → [Configuration – Worked Station Database Settings](Configuration#worked-station-database-settings)
+The input sources provide different levels of detail:
+
+| Source | Global callsign status | Per-band status | Grid square |
+|---|---:|---:|---:|
+| Simplelogfile | yes | no | no |
+| 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 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.
+
+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.

github_docs/en-User-Interface.md

@@ -26,14 +26,29 @@ The central table of all currently active chat users. Columns (depending on conf
 
 | Column | Content |
 |---|---|
-| Call | Station's callsign |
+| Callsign | Station callsign |
-| Name | Name from the chat name field |
+| Name | Name and additional information from the chat name field |
-| Loc | Maidenhead locator |
+| QRA | Maidenhead locator |
 | QRB | Distance in km |
 | QTF | Direction in degrees |
-| QRG | Automatically detected frequency |
+| QRG | Most recent frequency detected in a chat message |
-| AP | AirScout aircraft data (when active) |
+| Tropo | Result of the band-specific tropo or path assessment |
-| Band colours | Worked / NOT-QRV status per band |
+| Score | Current priority score |
+| Act | Minutes since the most recent activity |
+| AP | AirScout aircraft data, when enabled |
+| worked | Per-band Worked, band-opportunity and grid-square status, plus `wkdany` |
+| NOT QRV @ | Bands on which the station has manually been marked not QRV |
+| Category | Chat category of this entry |
+
+### Worked, band and grid-square status
+
+The subcolumns under **worked** use compact codes because several enabled bands leave little room for full descriptions. `X` marks a callsign worked on that band. `a` and `B+` identify an offered band which has not yet been worked. An appended `o` means that the four-character grid square has already been worked on this band.
+
+The **wkdany** subcolumn is band-independent: `x` means that the callsign has been worked, `o` means that the grid square has been worked on any band, and `xo` means both.
+
+Each status cell has a tooltip containing the legend and the state derived for that station. For the complete calculation, including NOT-QRV precedence, see [Worked Callsigns, New Bands and New Grid Squares](en-Features#worked-callsigns-new-bands-and-new-grid-squares).
+
+![Band-specific Worked status and worked grid squares](worked_band_status.png)
 
 **Sorting**: Click column headers. QRB sorting is numerical (corrected in v1.22).
 
@@ -53,20 +68,46 @@ Input field for the current antenna direction. Used for the planned `MYQTF` vari
 
 ## Filters
 
-The filter bar (from v1.21 as a flowpane for small screens):
+The filter bar is located above the chat-member table and groups related controls:
 
-- **Show only QTF**: Activate direction filter (N/NE/E/… buttons or degree input)
+- **Show only QTF** limits the list to a selected antenna direction.
-- **Show only QRB [km] <=**: Activate distance filter (toggle button)
+- **Show only QRB [km] <=** sets a maximum distance.
-- **Hide Worked [Band]**: Hide worked stations per band (one toggle per band)
+- **Find** searches for a callsign.
-- **Hide NOT-QRV [Band]**: Hide NOT-QRV-tagged stations per band
+- **wkd** hides callsigns which have already been worked on at least one band.
+- The individual band buttons hide a station if it has already been worked on that band or has been marked NOT QRV there. Only bands enabled for the local station are shown.
+- **Only new grids** shows only stations in four-character grid squares which have not been worked on any band.
+- **Grid color** is not a filter. It marks the QRA cell of an already worked grid square without hiding stations.
+- **New bands** shows stations with at least one detected, locally enabled and unworked band opportunity. NOT-QRV marks take precedence.
+- **Reachability**, **Tropo >=0dB** and **AS next 5m** limit the list according to the selected path or AirScout criteria.
+
+The filter bar has no fixed width. QTF, Worked and Reachability controls initially use the available space in their respective rows. When the horizontal divider is moved to the right and the chat-member area becomes narrower, controls wrap only when their actual required width no longer fits.
+
+![Wrapped filter bar in a narrow chat-member view](filter_bar_wrapped.png)
+
+In plain terms: the filters determine the table contents, but no longer enforce the minimum width of the entire right-hand side. The bar remains compact in the normal layout and uses additional height only when the view becomes genuinely narrow. Moving the divider back to the left immediately returns the controls to the available rows.
 
 ---
 
 ## Station Info Panel (Further Info)
 
-Bottom right: Shows all messages of a selected station (CQ messages and PMs in one panel). A message filter can be pre-configured via the default filter in the Preferences.
+The lower-right panel combines the messages associated with the selected station. This includes public messages, private messages to the local station and, where visible in the chat, private messages addressed to other stations.
 
-**Sked reminders** can also be activated here.
+The selected filter controls which of these messages are displayed. Under **Settings → GUI**, the default filter can be set to:
+
+- all messages,
+- private messages to the local station,
+- private messages to other stations, or
+- public messages.
+
+This setting changes the Further Info display only. Messages are neither discarded nor removed from the other message tables, and the filter can be changed at any time for the currently selected station.
+
+The lower part of the panel contains per-band **Not QRV** marks for the selected station. Individual controls are shown for the bands enabled in the local station settings. **tag not qrv all** sets or removes the mark for every supported band, including bands which are not currently visible.
+
+The change immediately affects the **NOT QRV @** column, band opportunities and the corresponding filters. It is stored in the internal database and restored after a restart.
+
+![Per-band NOT-QRV marks in the Further Info panel](not_qrv_controls.png)
+
+Sked reminders for both sked partners can also be enabled here.
 
 ---
 
@@ -100,6 +141,7 @@ If you encounter display problems: delete the configuration file → KST4Contest
 ## Operating Tips
 
 - **Keep the settings window open**: Quick access to enable/disable the beacon.
-- **Right-click in the user list**: Opens the snippet menu and further actions (QRZ.com profile, set NOT-QRV tags).
+- **Right-click in the user list**: Opens the snippet menu and other context actions.
+- **Mark a station NOT QRV**: Select the station and use the per-band controls in the **Further Info** panel.
 - **Enter from anywhere**: When text is in the send field, Enter sends directly – even if the focus is elsewhere.
 - **Stop the beacon**: Switch off the beacon while scanning frequencies to avoid flooding the chat with messages.