Motion capture: profile support, FPS config, persistent tracking, window state

Profile integration:
- CameraDevice.get_save_config() serialises camera_index, simulate,
  resolution, fps — cameras now persist in .labdaq profiles
- ProfileManager.register/unregister_device_factory() lets plugins
  register their device classes for profile restoration without
  core → plugin dependency
- MotionCapturePlugin registers CameraDevice factory on load/unload

Camera configuration:
- Add Frame Rate combo to CameraPanel (Default/15/24/30/60/120 fps)
  defaults to 30 fps; flows through to CAP_PROP_FPS on connect
- tracker.start() accepts fps param alongside existing resolution

Tracking persistence:
- CameraTracker.is_running() — checks thread alive state
- MotionCaptureWindow initialises _connected from tracker.is_running()
  so reopening the window resumes the live feed without restarting
  the camera or losing the active tracking state

Window state:
- Plugin saves px_per_mm + camera_idx when window closes
- Reopened window restores saved values and syncs mode/shape UI
  from tracker state via restore_ui_state() (signals blocked to
  avoid resetting tracker)
- Window type changed to Qt.WindowType.Window for independent
  close button on all Linux WMs

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

0 files changed, 0 insertions, 0 deletions