Say when the entry has two signals on the air

N1MM blocks the transmitter when a multi-operator entry is about to break
its own class. This program does not touch the transmitter: a logger that
decides for itself when the operator may not send loses a contact every
time it is wrong, and it is wrong whenever it has stale information about
the other stations — which, on a network, is whenever a laptop has just
been unplugged.

So the entry window says so instead. While this station is transmitting
and the entry is over what it is allowed, a red box goes across the top of
the window naming the station and the band. It is above the frequency and
under the menu, so nothing it covers is anything the operator needs while
he is sending, and it is big enough to read from the other side of the
room.

`TransmitRules` is what it asks:

| Entry | Allowed |
|---|---|
| one transmitter | one signal |
| two transmitters | two signals, on different bands |
| anything else | one signal per band |

Two on one band is wrong in every multi-operator class, so it is checked
whatever the category says. A station that has not said which band it is on
counts as somewhere else: a guess there puts the box in front of an
operator doing nothing wrong.

This is also the first thing that sends `XMIT`. The message was written and
nothing called it, so the transmit column of everybody's network status
window stayed empty and no station knew when another was sending. The entry
window now says when its key goes down and what it is sending.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PdAYHcdRktqKry7nk414TU

docs/unfinished.md

@@ -405,9 +405,18 @@ by hand stays closed until it is opened again, because the next beacon would
 otherwise open it within ten seconds. The Resynchronize and Rescore tabs work
 on a period — the contest, since a time, or the last few hours. Options holds
 what there is something behind: Log QSOs at all Stations, the message trace, and
-Run1/Run2. Left out are the transmit interlocks — this program does not block a
-transmitter, and a station that claimed it did would be waited on for nothing —
-and the two telnet options, which wait on the master relaying cluster spots.
+Run1/Run2. Left out are the two telnet options, which wait on the master relaying cluster
+spots.
+
+**Two signals at once.** N1MM blocks the transmitter when the entry is about to
+break its own class. This program does not touch the transmitter — a logger that
+decides for itself when the operator may not send loses a contact every time it
+is wrong — so the entry window puts a red box across its top instead, naming the
+other station and the band. `TransmitRules` holds what is allowed: one signal in
+a one-transmitter entry, two on different bands in a two-transmitter entry, and
+never two on one band whatever the class. A station that has not said which band
+it is on counts as somewhere else, because a guess there puts the box in front of
+an operator doing nothing wrong.
 
 **What the entry agrees on.** Four things have to match across the stations of
 an entry, and each is now checked rather than assumed: