Skip to content

iOS: consume camera capabilities for live chrome #126

Description

@erik-sutton95

Maintainer task. Parent: #124. Depends on the core table sub-issue. Product discussion: #123

Goal

iOS live chrome, chrome editor, and Operator Setup hide controls the connected body cannot do. Operator prefs cannot resurrect a stick on a non-gimbal body.

Already in tree

Stick mounts from chromeSectionMounts(.gimbalStick) only. AF rows already use supportsFocusMode. Nano hide-stick is still a checkbox on #83 / #79, not implemented.

Do

  • Gimbal stick, recenter, flip, stick throw 1–5: only if hasGimbal
  • Chrome editor omits .gimbalStick (and any other gimbal chrome) when the body has no gimbal
  • Operator Setup hides gimbal throw / future speed+mode rows without gimbal
  • Layout: no reserved stick well on Nano portrait/landscape (MonitorPortraitLayout / LiveMonitorLayout)
  • Capture sheets / AF keep using the existing focus flags from the same table
  • Switching saved cameras remounts chrome for the new body without a relaunch

Out of scope

Android (sibling). Wiring gimbal speed/mode SETs (#79) — only the visibility of that chrome.

Done when

Physical Nano: no stick, no recenter/flip, no gimbal throw in Setup. Physical Pocket 4 Pro: stick still works. #83 / #79 “hide gimbal on Nano” can tick once this lands.

Verify

Physical Pocket 4 Pro + Nano. just native-check.

Metadata

Metadata

Assignees

Labels

area:controlCamera control (record, mode, and related commands)area:iosiOS SwiftUI shell (ios/OpenPocketCine)area:live-viewLive view streaming, rendering, and related pipelinearea:uiGeneral UI/UX, layout, design systemenhancementNew feature or requestreadyTriaged and ready to pick up

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions