You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Atemschutz: a double-click on RÜCKZUG also triggers ABGENOMMEN, and neither can be undone #601
Split out of the UX review #262. This is safety-critical: it can end the monitoring of a crew without anyone meaning to.
Problem
In the Atemschutz grid and the cards, an active Trupp shows [Druck] [DRUCK] [RÜCKZUG]. Once RÜCKZUG is clicked, the row immediately shows [Druck] [DRUCK] [ABGENOMMEN]. ABGENOMMEN lands in exactly the slot RÜCKZUG just left, with the same signal style (ScbaView.axaml:393-402, cards :525-534).
A double-click on RÜCKZUG therefore withdraws the Trupp and marks it removed in one gesture. Its monitoring ends: the timer stops, it leaves the alarm set, and two ETB lines are written.
None of the state transitions (IM EINSATZ, RÜCKZUG, ABGENOMMEN) asks for confirmation or offers an undo. Withdraw() and MarkRemoved() call straight through to the session (ScbaViewModel.cs:229-237, :1069-1094). The app already has an undo notice, OfferUndo / UndoNoticeViewModel with Strg+Z (#543), but only ticking off an Aufgabe uses it. ScbaViewModel is constructed without it.
Expected
A double-click on RÜCKZUG must never also trigger ABGENOMMEN.
or a "Rückgängig" notice with Strg+Z, the way Aufgaben do.
RÜCKZUG is time-critical and must stay one action. An undo notice fits it better than a dialog.
Notes
Write the failing test first. A headless test should replay two clicks on the RÜCKZUG button's position within the double-click interval, then assert the Trupp is still withdrawing and still monitored.
ETB entries are a record. An undo should either suppress the ETB line until the notice expires or write a correcting line. Decide which in the PR.
Activity