# `Events['camera:control-start']`

> Contract 2.0.0 · package sha256 `a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e` · generated from `configurator-runtime.d.ts` by `services/onsite-scripter/scripts/build-contract-docs.mjs`; edit the source, not this file.

Property of [`Events`](Events.md) · stable · since 2.0.0

```ts
'camera:control-start': void;
```

The shopper started a pointer or touch gesture: orbiting, panning or a two-finger pinch. A
mouse wheel, or a touchpad scroll or pinch, is not a gesture, as in 1.x (its camera emits no
start or end for it): it fires neither event, doesn't pause `autoRotate` and doesn't take a
running view move over; it changes the distance that move lands at, and the move resolves
when it lands. Like any camera motion it fires 'camera:changed' and 'camera:rest'. Keep your
own "is interacting" flag from this pair.

## Generic-API test (spec 3.1)

| Rule | Result |
| --- | --- |
| 1. Neutral name | pass: `camera:control-start` names no product |
| 2. A precedent | pass: [model-viewer (ar, camera-orbit, auto-rotate)](https://modelviewer.dev/docs/) (row `G41`) |
| 3. Two apps, or labs | pass: 21 apps (ledger: app-fc306ec3dc; fleet cross-check: app-04c2774145, app-0c773a4ee3, app-37356bf09f, app-378d190f1b, app-4762caacdc, app-4fd23bc869, app-822bb9d6aa, app-8675b3225c and 13 more) |
| 4. The cheaper fix first | decided per need in Appendix B: rows `G41` at tier stable (a member only where no rule, data, asset or app code serves the need) |