From e9e5ec79cdb8ec143277c1db644735680ff542c1 Mon Sep 17 00:00:00 2001 From: leonarski_f Date: Fri, 19 Jun 2026 16:01:13 +0200 Subject: [PATCH] frontend: phi_min/phi_max columns in the azimuthal ROI table Surface the optional azimuthal phi-sector bounds (phi_min_deg/phi_max_deg) as editable columns, so a sector can be set from the web UI, not only the viewer. Also fix the Q_max row's d header, which read d_max but is d_min. Co-Authored-By: Claude Opus 4.8 --- frontend/src/components/ROI.tsx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/frontend/src/components/ROI.tsx b/frontend/src/components/ROI.tsx index 5e0a43bc..59be05a7 100644 --- a/frontend/src/components/ROI.tsx +++ b/frontend/src/components/ROI.tsx @@ -318,8 +318,12 @@ function ROI({s: serverS}: MyProps) { } else return row; }, - renderHeader: () => (
dmax [Å]
) + renderHeader: () => (
dmin [Å]
) }, + { field: 'phi_min_deg', type: 'number', editable: true, + renderHeader: () => (
φmin [°]
) }, + { field: 'phi_max_deg', type: 'number', editable: true, + renderHeader: () => (
φmax [°]
) }, { field: 'actions', type: 'actions', width: 50, cellClassName: 'actions', getActions: (id : GridRowModel) => { return [