Render preview uses the shared camera navigation (#1462)

* Render preview uses the shared camera navigation The Render workspace's product preview had its own hard-coded camera controls. Camera input now lives in one component, navigation::handle, which the modelling viewport and the Render preview both call (NavCaps: orbit, pick). Render gets the navigation preset, Orbit around, zoom to the cursor, the middle double-click and the axis view or navigation cube. Flat pages can call it with orbit off. A test rejects pages that read the wheel or move the camera themselves. Fixes #1454 Co-Authored-By: Claude Opus 5.5 <[email protected]> * Render panel hint says the camera moves as in Design Co-Authored-By: Claude Opus 5.5 <[email protected]> --------- Co-authored-by: Claude Opus 5.5 <[email protected]>
2026-10-15 13:48:05 -04:00
1 parent e8e2ccc8a9
commit be985f136d
@@ -43,7 +43,9 @@ discards staged settings. Draft settings are separate for each open document.
 **Restore Saved Camera** runs `render.settings.apply {name}`, preserving target,
 distance, yaw, pitch, roll, FOV and up axis as view state. It neither edits the document
 nor settles a stale model. The UI honours its up axis in Render; the Design camera
-is restored when returning. Drag orbits, middle-drag pans, scrolling zooms, and
+is restored when returning. The camera moves exactly as in Design: the navigation preset,
+Orbit around, zoom to the cursor, the SpaceMouse, the middle double-click, F6 and the axis
+view or navigation cube all work (nothing is picked or selected here), and
 **Fit Product** frames visible product bodies without including sketches or selection.

 Preview drafts do not make the document dirty until saved. Unknown backend preferences