/**
 * Pure camera-framing math for the right panel's OrbitControls.
 *
 * Deliberately free of DOM / copperScene / OrbitControls: every mistake here shows
 * up only as "rotation feels wrong" and never throws, so it must be unit-tested.
 * The wiring lives in Copper3dOrbitControls.ts.
 */
import * as THREE from 'three';
/** Shape of src/assets/nrrd_view*.json. */
export interface CameraViewPreset {
    farPlane: number;
    nearPlane: number;
    eyePosition: number[];
    targetPosition: number[];
    upVector: number[];
}
export interface Framing {
    /** Rotation pivot = bounding-box centre (decision C4). */
    pivot: THREE.Vector3;
    /** Bounding-box diagonal length; view-independent, shared by all three presets. */
    size: number;
    /** Camera-to-pivot distance (decision C5 auto-framing). */
    dist: number;
}
export interface ViewPose {
    position: THREE.Vector3;
    up: THREE.Vector3;
    target: THREE.Vector3;
}
/** Leave ~30% margin so the model does not touch the panel edge while pan/rotating. */
export declare const FRAMING_MARGIN = 1.3;
/**
 * Whether this gesture is a pure rotate. Used to decide whether to snap the rotation
 * pivot back to the model centre: OrbitControls' pan moves target with the camera, so
 * after a pan target is off the model and a rotate would orbit an empty point. We snap
 * target back on rotate start, but must NOT on pan/dolly (or the model jumps at pan start).
 *
 * Picking the wrong state constant is a silent bug (rotate not re-pivoting, or pan wrongly
 * re-pivoting), so it is unit-tested.
 */
export declare function isRotateGesture(state: number): boolean;
/**
 * Bounding box -> pivot + size + framing distance.
 *
 * fovDeg is read from the camera by the caller at runtime (copper3d uses 75); it is
 * not hardcoded here.
 */
export declare function computeFraming(box: THREE.Box3, fovDeg: number): Framing;
/**
 * Preset + pivot + distance -> camera pose.
 *
 * The preset's eyePosition is absolute; only its DIRECTION is taken here, and the
 * distance comes from C5 auto-framing (the implicit 600 in the JSON is ignored).
 *
 * up must be Gram-Schmidt-orthogonalised against the view direction (decision D1):
 * OrbitControls uses camera.up as its polar axis, and nrrd_view_coronal.json's up
 * (0,1,-1) is not perpendicular to its own view direction (0,1,0) — feeding it raw
 * gives a 45-degree-tilted pole. The old trackball path got away with it only because
 * three's lookAt() orthogonalises internally.
 */
export declare function resolveViewPose(preset: CameraViewPreset, pivot: THREE.Vector3, dist: number): ViewPose;
/**
 * Far clipping plane (decision D2).
 *
 * The preset's farPlane is 1000, but a large volume's maxDistance (= size*5) can
 * exceed it, which would clip the model when the user zooms all the way out.
 *
 * The Number.isFinite guard is required: right after construction and before the first
 * frameBox, OrbitControls' maxDistance is still the default Infinity.
 */
export declare function resolveFarPlane(presetFar: number, maxDistance: number, dist: number): number;