maziggy 529155413f fix(ams): show "?" for loaded-but-unconfigured AMS slots (#1694) ...

Reporter on a 3-AMS P1S saw slots labelled "Empty" even though spools
  were physically loaded - OrcaSlicer's Device view showed the same
  slots as loaded.

  Root cause: the compact label below the AMS slot circle rendered
  tray.tray_type || t('ams.slotEmpty'), falling back to "Empty" whenever
  the printer firmware hadn't been told which material is in the slot.
  getEmptySlotKind already distinguishes 'physical' (firmware confirmed
  empty via state 9/10) from 'reset' (tray_type absent but firmware
  hasn't confirmed empty - spool loaded, just unassigned). The hover
  card and circle border already used that distinction; the compact
  label did not.

  Fix: label branches on emptyKind - 'physical' keeps "Empty", 'reset'
  shows "?" matching the slicer's own convention. External / VT tray
  label is unchanged (external trays have no "configured/unconfigured"
  distinction - they're either loaded or not). SpoolBuddy AmsUnitCard
  carried the same bug and got the same fix plus a tooltip.

2026-06-09 08:41:46 +02:00

..

index-BBXh9elm.js

fix(ams): show "?" for loaded-but-unconfigured AMS slots (#1694)

2026-06-09 08:41:46 +02:00

index-BvmIMSUd.css

feat(print-log): per-row delete on Print Log page (#1687 part 1)

2026-06-09 07:54:27 +02:00