Repository navigation
[Remote rendering 3.3] Server-authoritative widget state聽#21
Description
Activity
- added a parent issue
on Aug 25, 2026 Added four PRs that together move widget state authority to the server.
- feat: [Remote rendering 3.3a] server-authoritative widget toggles and projection聽#137
- Syncs four widget toggles to the server: cross section widget, wire frame widget, orthographic view widget, bounding box widget
- After this, the off/on state of those widgets is preserved across a page refresh or new connection, and save/load state read from/apply to the server's VTK pipeline
- feat: [Remote rendering 3.3b] fold per-part edge visibility into the global toggle聽#138
- Refactor only: cleans up the per-part edge visibility into the global toggle (we don't currently support per-part wire frame controls, so we don't need per-part state to reflect it)
- feat: [Remote rendering 3.3c] server-authoritative cross-section plane聽#139
- Syncs the cross-section plane to the server
- After this, the cross-section plane origin and normal preserved across a page refresh or new connection, and save/load state read from/apply to the server's VTK pipeline.
- One known defect: on load_state, if the saved state's cross-section widget visibility is true, the correct state loads (including the plane origin/normal values), but the plane doesn't initially render. Clicking the cross-section widget toggle twice makes it appear. The fix is deferred until user story 3.6 (#24), where we revisit the save/load state end to end mechanism once ownership of all the viewer state is held by the server.
- feat: [Remote rendering 3.3d] sync camera to server on orientation widget聽#143
- Camera changes originating from the orientation widget are now synced to the server, and are preserved across a refresh/reconnect
- feat: [Remote rendering 3.3a] server-authoritative widget toggles and projection聽#137
馃摑 Description of the feature
Sync back the widget state to the server. For toggles (on/off) this can be immediate. For the actual widget interaction, the updated widget state is synced back to the server when the interaction ends (e.g. on mouse-up). When the updated widget state gets synced back to the server, it is applied on the server's vtk pipeline, but a local_view.update() is not triggered, and no round trip is triggered. (this is deferred till phase 6).
Further detail to be added in backlog grooming.
Acceptance Criteria
馃挼 Business Value
No response
馃敆 Useful links and references
No response