From 658e5c2224e56c6d815344f96801884891b2617b Mon Sep 17 00:00:00 2001 From: cproudlock Date: Wed, 5 Aug 2026 15:37:46 -0400 Subject: [PATCH] Give the calendar room, and put new notifications on the shopfloor board The calendar was set to height 'auto', which sizes each week row to its own content, so a month of mostly empty days collapsed into thin strips. It now takes a viewport-relative height and expandRows shares that evenly across the weeks, with a floor under each day cell so a short window squeezes the grid back down rather than the rows vanishing. New notifications now have "Show on Shopfloor Dashboard" ticked. The board is where these are meant to be read, and starting unticked meant most were written and then never appeared on it. Only the default for a NEW notification. Editing an existing one still loads its stored value, so nothing that was deliberately turned off gets flipped back on, and the column default is left alone so an API or import caller that omits the field keeps the behaviour it has today. --- .../frontend/views/CalendarView.vue | 787 +++++++++--------- .../frontend/views/NotificationForm.vue | 7 +- 2 files changed, 409 insertions(+), 385 deletions(-) diff --git a/plugins/notifications/frontend/views/CalendarView.vue b/plugins/notifications/frontend/views/CalendarView.vue index 7bdde03..bdb5eb2 100644 --- a/plugins/notifications/frontend/views/CalendarView.vue +++ b/plugins/notifications/frontend/views/CalendarView.vue @@ -1,384 +1,403 @@ - - - - - + + + + + diff --git a/plugins/notifications/frontend/views/NotificationForm.vue b/plugins/notifications/frontend/views/NotificationForm.vue index 9087a22..a48fff2 100644 --- a/plugins/notifications/frontend/views/NotificationForm.vue +++ b/plugins/notifications/frontend/views/NotificationForm.vue @@ -275,7 +275,12 @@ const form = ref({ starttime: '', endtime: '', isactive: true, - isshopfloor: false, + // Ticked for a NEW notification: the shopfloor board is where these are + // meant to be seen, and leaving it off by default meant most were written + // and then never appeared there. Editing an EXISTING notification still + // loads its own stored value (see loadNotification), so this never flips a + // setting somebody deliberately turned off. + isshopfloor: true, employeesso: '' })