Skip to content

Atemschutz: an acknowledged alarm looks exactly like an unacknowledged one #654

Closed

Description

@DeepDiver1975

Split out of the UX review #262.

Problem

ALARM QUITTIEREN in the workspace header silences every Trupp. Once pressed, nothing on screen shows that the alarm has been acknowledged:

  • IsAlarmAcknowledged is not bound in any .axaml; the header binds only the command (IncidentWorkspaceView.axaml:305-306).
  • CanAcknowledgeAlarm => IsAnyAlarm (ScbaViewModel.cs:671-681), so the button stays enabled and looks exactly as before.

A second Atemschutzüberwacher walking up to the ELW cannot tell whether a red, silent banner means "acknowledged" or "audio broken". Pressing again does nothing visible. Acknowledging a safety alarm has to be a visible state, not a hidden flag.

What already works: a Trupp that goes into alarm after the acknowledgement re-arms it (UpdateAlarm, :690-695).

Expected

  • After acknowledgement, the button is disabled and the banner says so ("QUITTIERT", or a distinct style class), until a new Trupp trips the alarm.
  • Per-Trupp acknowledgement is out of scope here; this issue only makes the existing global state visible.

Notes

  • Tests: acknowledge, assert CanAcknowledgeAlarm is false and the banner shows the acknowledged state; then trip a second Trupp, assert the alarm re-arms and the button is live again (pin the existing behaviour).
  • This touches the UI, so the PR needs a before/after screenshot pair.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestuxUser interface and usability

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions