@osamash/floor-planner 1.2.4 → 1.2.6

package/dist/types/react-planner/utils/index.d.ts

@@ -5,9 +5,10 @@ import * as SnapUtils from "./snap";
 import * as SnapSceneUtils from "./snap-scene";
 import * as history from "./history";
 import * as ObjectUtils from "./objects-utils";
+import * as LineFamilyUtils from "./line-family";
 import IDBroker from "./id-broker";
 import NameGenerator from "./name-generator";
-export { GeometryUtils, GraphInnerCycles, MathUtils, SnapUtils, SnapSceneUtils, history, IDBroker, NameGenerator, ObjectUtils, };
+export { GeometryUtils, GraphInnerCycles, MathUtils, SnapUtils, SnapSceneUtils, history, IDBroker, NameGenerator, ObjectUtils, LineFamilyUtils, };
 declare const _default: {
     GeometryUtils: typeof GeometryUtils;
     GraphInnerCycles: typeof GraphInnerCycles;
@@ -18,5 +19,6 @@ declare const _default: {
     IDBroker: typeof IDBroker;
     NameGenerator: typeof NameGenerator;
     ObjectUtils: typeof ObjectUtils;
+    LineFamilyUtils: typeof LineFamilyUtils;
 };
 export default _default;

package/dist/types/react-planner/utils/line-family.d.ts

@@ -0,0 +1,29 @@
+/** Surfaces (patios, lawns, decking…) are drawn with the very same `lines` +
+ *  `vertices` machinery as walls — but they are not structure. A patio laid
+ *  over a room must not weld itself onto the walls it crosses, must not split
+ *  them, and must not turn the room's floor into part of the patio.
+ *
+ *  So every graph operation works inside one *family* at a time: two lines
+ *  only share a vertex, split each other, merge when colinear, or take part in
+ *  the same area cycle when their families match. Snapping is deliberately
+ *  exempt — a surface should still be able to land exactly on a wall corner,
+ *  it just must not become attached to it.
+ */
+export type LineFamily = "surface" | "structure";
+export declare const SURFACE_LINE_TYPE = "surface";
+export declare function lineFamily(type?: string | null): LineFamily;
+export declare function lineFamilyOf(line: any): LineFamily;
+/** Whether a vertex may be shared with a line of `family`.
+ *
+ *  A vertex nothing is hanging off yet takes anything. Otherwise it belongs to
+ *  the families of the lines already attached — which is normally exactly one,
+ *  but plans saved before families existed can have vertices where a wall and
+ *  a surface already meet. Those stay usable by both rather than being split
+ *  apart underneath a scene that is already drawn.
+ */
+export declare function vertexAcceptsFamily(vertex: any, layer: any, family: LineFamily): boolean;
+/** The family of an area, read off the lines meeting at its corners. Mirrors
+ *  `getAreaKind`'s rule: an area is a surface only when nothing structural
+ *  borders it. */
+export declare function areaFamily(area: any, layer: any): LineFamily;
+export declare const LINE_FAMILIES: LineFamily[];

package/dist/types/react-planner/utils/screenshot.d.ts

@@ -1 +1,22 @@
-export declare const getSVGScreenshot: () => Promise<string>;
+export interface ScreenshotOptions {
+    /** Cap output width in px (height scales to match). Omit for 1:1 with the SVG. */
+    maxWidth?: number;
+    /** Output MIME type. Default "image/png". */
+    type?: string;
+    /** Quality 0-1, for lossy types only. Ignored for PNG. */
+    quality?: number;
+    /**
+     * Reject if the largest SVG on the page is narrower than this. The viewer2d
+     * SVG is unmounted in 3D mode, and without this the "largest SVG" would be a
+     * ~28px toolbar icon, silently producing a thumbnail of an icon.
+     */
+    minWidth?: number;
+    /** Overall budget in ms. Default 15000. */
+    timeout?: number;
+}
+/**
+ * Rasterize the plan viewer's SVG to a data URI. Rejects (rather than hanging)
+ * when there's nothing capturable on screen, an asset can't be decoded, or the
+ * whole thing overruns `timeout`.
+ */
+export declare const getSVGScreenshot: (options?: ScreenshotOptions) => Promise<string>;

package/dist/types/react-planner/utils/visual-change.d.ts

@@ -0,0 +1,12 @@
+import type { ReactPlannerStore } from "../../store/ReactPlannerStore";
+/**
+ * Did anything the 2D viewer paints change — and nothing that doesn't?
+ *
+ * Scene identity is too blunt to drive this. Selection is drawn, so it changes
+ * the pixels and the byte-comparison downstream won't filter it either: left
+ * alone, idly clicking around a finished plan re-uploads a thumbnail per click,
+ * each with a different element highlighted. Geometry, layer visibility, the
+ * viewport box and the view options that live outside the planner record are
+ * what count.
+ */
+export declare function hasVisualChange(next: ReactPlannerStore, prev: ReactPlannerStore): boolean;

package/dist/types/react-planner/viewer2d/Area.d.ts

@@ -3,6 +3,12 @@ interface AreaProps {
     area: any;
     layer: any;
     catalog: Catalog;
+    /** Which of the two passes this is. Fills and labels are drawn separately
+     *  so every label lands above every fill — a surface laid over a room is
+     *  meant to cover the room's floor, but not to swallow its name. Both
+     *  passes iterate the same ordered list in
+     *  [Layer.tsx](src/react-planner/viewer2d/Layer.tsx). */
+    part?: "fill" | "label";
 }
-export default function Area({ layer, area, catalog }: AreaProps): import("react/jsx-runtime").JSX.Element;
+export default function Area({ layer, area, catalog, part, }: AreaProps): import("react/jsx-runtime").JSX.Element | null;
 export {};

package/dist/types/react-planner/viewer3d/viewer3d.d.ts

@@ -69,6 +69,16 @@ export default class Scene3DViewer extends React.Component<Viewer3DProps> {
      * shadows for a scene that is still half loaded.
      */
     private invalidateShadows;
+    /**
+     * Bound the dolly range to the size of what's being looked at, so you can
+     * neither fly halfway to the sun nor end up inside a wall.
+     *
+     * Re-derived when the extent changes, because the box measured at mount is
+     * the grid's — the size of the whole scene rather than of the plan drawn in
+     * it — and limits taken from that stop the camera well short of a small
+     * plan.
+     */
+    private applyZoomLimits;
     /**
      * Dolly toward (factor > 1) or away from (factor < 1) the orbit target.
      * OrbitControls' own min/maxDistance still bound the result, so the buttons

package/package.json

@@ -11,7 +11,7 @@
   "files": [
     "dist"
   ],
-  "version": "1.2.4",
+  "version": "1.2.6",
   "type": "module",
   "scripts": {
     "dev": "vite",

package/dist/types/react-planner/hooks/useScreenshotBeforeUnload.d.ts

@@ -1,4 +0,0 @@
-export declare function useScreenshotBeforeUnload(onReady?: (img: string) => void): {
-    ensureScreenshot: () => Promise<void>;
-    screenshotDone: import("react").RefObject<boolean>;
-};