/**
 * OrientationDriftModal — informational popup shown when the SDK
 * auto-abandons an in-progress capture because the device rotated
 * between Mode A (landscape + vertical pan) and Mode B (portrait
 * + horizontal pan) mid-flight.
 *
 * ## When this modal appears
 *
 * In the v0.12 `<Camera>` integration, the modal is rendered while
 * `useOrientationDrift(active).drifted === true`.  By the time the
 * modal renders, the capture has ALREADY been stopped (the
 * `<Camera>` component's drift effect calls the engine's `stop()`
 * the same render).  The modal exists solely to explain to the
 * user what happened — no "Continue" / "Resume" affordance because
 * the engine docstring at `incremental.ts:373-403` is explicit
 * that cross-mode capture is "best-effort, not supported" and
 * continuing past drift produces malformed output.
 *
 * ## Layer-2 host usage
 *
 * Hosts using `CameraView` directly (rather than the flagship
 * `<Camera>`) can compose this modal with `useOrientationDrift`
 * for the same auto-abandon UX:
 *
 *   const drift = useOrientationDrift(captureActive);
 *   useEffect(() => {
 *     if (drift.drifted) {
 *       // host abandons capture (engine stop + state cleanup)
 *       stopCapture();
 *     }
 *   }, [drift.drifted]);
 *
 *   return <>
 *     <CameraView ... />
 *     <OrientationDriftModal
 *       visible={drift.drifted}
 *       captureOrientation={drift.captureOrientation}
 *       currentOrientation={drift.currentOrientation}
 *       onAcknowledge={dismissDriftModal}
 *     />
 *   </>;
 *
 * ## Accessibility
 *
 * Modal `role` defaults to RN's native dialog handling.  The OK
 * button carries an `accessibilityRole='button'` + label.  Body
 * text uses `accessibilityRole='text'` so the orientation summary
 * is read by VoiceOver / TalkBack.
 */
import React from 'react';
import { type DeviceOrientation } from './useDeviceOrientation';
export interface OrientationDriftModalProps {
    /**
     * v0.25 — counter-rotation (degrees) so the popup reads upright at the
     * PHYSICAL device orientation even though the camera window is
     * portrait-locked.  Pass `contentRotationDeg(jsLandscape,
     * deviceOrientation)` (what <Camera> uses for its control content);
     * 0/undefined = no rotation (legacy).
     */
    contentRotationDeg?: number;
    /**
     * Show / hide.  In the `<Camera>` integration this is driven by
     * the latched `drifted` flag from `useOrientationDrift`.
     */
    visible: boolean;
    /**
     * Orientation the capture started in.  Shown in the body copy
     * ("Capture started in PORTRAIT") so the user understands the
     * baseline.  `undefined` is tolerated (the modal hides the line);
     * the prop is optional only to mirror `useOrientationDrift`'s
     * return shape (which has `undefined` when inactive).  When the
     * modal is `visible`, drift detection means this was non-
     * undefined at the moment the flag latched — so undefined here
     * is unlikely in practice.
     */
    captureOrientation: DeviceOrientation | undefined;
    /**
     * Current device orientation.  Shown in the body copy ("now
     * LANDSCAPE-LEFT") so the user understands what changed.
     */
    currentOrientation: DeviceOrientation;
    /**
     * Tapped when the user dismisses with OK.  By the time the
     * modal renders the capture is already stopped; this callback
     * exists only to clear the latched drift state so the next
     * capture can start fresh.
     */
    onAcknowledge: () => void;
}
export declare function OrientationDriftModal(props: OrientationDriftModalProps): React.JSX.Element;
//# sourceMappingURL=OrientationDriftModal.d.ts.map