From d23c4c4037044e3af8dd43d78bb7c7bf6e9bdec9 Mon Sep 17 00:00:00 2001 From: rouggy Date: Sat, 1 Aug 2026 00:50:48 +0200 Subject: [PATCH] fix: RST fields too narrow for a 59+30 report MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I took the callsign field's extra width from the RST pair, on the assumption that five characters was the most they would ever hold. A signal report of "59+30" is exactly five characters plus its padding, and it was clipped. The RST fields are back to their original width. The callsign keeps its extra room — the row has space for both. --- frontend/src/App.tsx | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/frontend/src/App.tsx b/frontend/src/App.tsx index eb213b6..c7eef20 100644 --- a/frontend/src/App.tsx +++ b/frontend/src/App.tsx @@ -3719,8 +3719,10 @@ export default function App() { // The callsign field is WIDER than the fields around it, deliberately: it is // the one field always typed into, it carries the REC badges on its right, and // a long portable call (VK9/OH1ABC/MM) must stay readable as it is entered. - // The room comes from the RST pair, which never needs more than five - // characters. + // It was widened by taking room from the RST pair — until a signal report of + // "59+30" turned up, which is five characters plus its padding and no longer + // fitted. The RST fields are back to their original width; the callsign keeps + // the rest of the row. const callsignBlock = (
); const rstTxBlock = ( -
+
{ setRstSent(v); rstUserEditedRef.current = true; }} />
); const rstRxBlock = ( -
+
{ setRstRcvd(v); rstUserEditedRef.current = true; }} />
);