49ab9179a7da498cbb3ea40ba6f94eb8be4e831b
1091
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
bcdbb91f26 |
Assemblies: one children-by-parent index for the occurrence walk (#12173)
Document::placements scanned every occurrence for each component it visited, so its cost was placements times occurrences, on every world placement. The new OccurrenceTree (crates/doc/src/occurrence_tree.rs) lists each component's children once, in one pass and in document order; placements walks it with the same order, caps and stop behaviour, through placements_with, which takes each occurrence's transform from the caller. inside_component reads the same index instead of scanning per component. Tests compare the walk with the scanning one on 13 shapes and on hostile generated documents, at its caps, in document order and with a given transform. Release, 97,540 placements: about 120 ms -> 15.5 ms, the same in either run order (docs/perf.md). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
796b7c40d3 | Regenerate generated files and fold pending files [skip ci] | ||
|
|
90d9c6488a |
Panels: add columns, stacks and tabs with exact drag previews (#11305) (#11608)
* claim: #11305 * Panels: add columns, stacks and tabs with exact drag previews (#11305) |
||
|
|
edb7882815 |
Appearance: browse themes in a carousel or grid, filter them, and set Day and Night themes (#12120)
* Appearance: theme picker with carousel, grid, filters and Day/Night slots * Appearance: theme picker arrows move a screenful of themes * Theme picker: translations, token metrics, wheel helper in navigation, reveal tolerance * Theme picker: keep both new Appearance preferences after the rebase * Appearance: adapt theme picker to egui 0.37 |
||
|
|
db3558d820 |
Extrude: the distance arrow snaps to a parallel face and outlines it (#2398) (#9688)
* claim: #2398 * Extrude: the distance arrow stops at a parallel face and outlines it (#2398) While Extrude's distance arrow is dragged, a flat face parallel to the profile and lying over it takes the distance exactly once the tip comes within 8 screen points of its plane, and the face is outlined as a hovered face is. A cut dragged through a block so stops at its far side. Faces beside the profile don't catch the arrow; Alt/Ctrl (free drag) turns it off. The distance stays a number in the existing parameter. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Extrude face stop: clippy (test-only current, +=) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Extrude face stops: a preference, on by default, keeps the old round steps (#2398) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Extrude face stops: follow world_state returning a Result (#2398) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Extrude face stops: import Vec/Plane from solidcore_record after the layer split Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: bherbruck <brennen.herbruck@gmail.com> |
||
|
|
9f2e117934 |
Revolve follows the highlighted sketch edge (#7452) (#7479)
* Revolve follows the highlighted sketch edge (#7452) Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> * Attribute the #7452 screenshots and recording Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Fix needless borrow in the revolve axis test Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: bherbruck <brennen.herbruck@gmail.com> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|
|
d5e953871b | Sketch Mirror: use the preselected construction line (#10486) | ||
|
|
8f20ad4532 | Regenerate generated files and fold pending files [skip ci] | ||
|
|
7e002f182d |
Opening a design from a newer SolidCraft: it opens with a notice instead of being refused (#12166)
* Open a design from a newer SolidCraft with a warning instead of refusing it A newer format number or an unknown change no longer blocks opening. What this version can read opens; a feature it can't read stays on the timeline with an error, and fields, sections and container parts it doesn't know are named in the reply and written back by Save, under the file's own number. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Saving a newer design from the CLI, and editing a feature this version can't read `run --save` writes a design holding a feature only a newer build can build; `--out` still stops, since it would export the part without that feature. Edit Feature on such a feature says why instead of opening the palette. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Translate the newer-design notice for the complete catalogs; clippy Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
f0d305a783 |
Move triad: dragging in large designs does less work per step (#7273) (#7276)
* claim: #7273 * Viewport: drag a component as a GPU layer of its own Each step of a Move triad drag placed the component anew, and the viewport then rebuilt the model scene and uploaded it again. The dragged bodies are now drawn from the scene built where the drag found them, moved on the GPU by the drag's motion; the rest of the model stays as it was. In the viewport a step meshes, builds and uploads no geometry; only the transform (and the ground shadow) changes. - gpu: Frame::moving draws a second scene with its own model matrix (U.model, applied in every vertex entry, instanced parts included); blocks, evaluated chunks and instanced triangles pass between the model scene and the layer instead of being uploaded again; glass is sorted in the layer's frame; the AO prepass and see-through pass cover it; the frame key includes the layer. - doc: ModelBody::display_moved_from gives the rigid motion between two worlds' copies of one solid. - ui-egui: the model scene without the dragged bodies is built once; dragged bodies are matched by name; the step's body boxes are the start boxes moved; selected or hovered dragged bodies light where they stand. A drag back where it began keeps its layer. A section, an analysis, continuity seams or no GPU draw the drag as before; capturing the move makes the scene whole again. * feat(ui): a setting to keep the highlight under the pointer while Move drags A Move triad drag drawn as a GPU layer picks nothing under the pointer, which keeps a step from meshing the dragged bodies where they stand and from looking up the Browser row a highlight follows. Preferences > Tools > Assembly Move > "Highlight what is under the pointer while dragging a component" (`move_drag_highlights`, off by default) picks and highlights as before. Also: the drag layer test takes `as_chunks` (clippy 1.99's `chunks_exact_to_as_chunks`). * fix(ui): say when the Move drag highlight setting applies The label names Move's arrows, and the tooltip says that with a section or an analysis shown the drag highlights all the same, and that a part dragged along its joints never does. |
||
|
|
dc33c4a24d |
Saving: designs with many threaded holes keep all saved states (#10601)
* claim: tap marking records once in the model cache * Model cache: write each tap marking record once and share it between states Problem: every state of a saved model wrote the cosmetic tap markings of all the features before it, so the records grew with the square of the features. A design of 400 marked cylinders wrote 34 of its 37 MB manifest that way: past the 32 MiB limit the save thinned the cache (590 of 806 states left out, opening evaluates them again) and wrote the manifest several times while choosing what to keep. Solution: the records keep a list of markings, each written once (keyed by its text, as the sheet bodies are); a state names its markings as runs of places, like its bodies and sketches. A marking at the same place in the state written just before, equal to the bit, is found without writing it as text. A thinned model keeps the whole list and counts it once; the reader counts the markings with what a state holds. The cache format is now /6: an older cache is a miss and the design is evaluated as before. The design document is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Saved model: count each tap marking by its text against the held limit A state clones every marking it lists, so a run repeating one large marking could hold far more than MAX_HELD items of memory. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Markus Kaltenbrunner <kaltenbrunnermarkus@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: bherbruck <brennen.herbruck@gmail.com> |
||
|
|
c1760d4857 |
Point clouds: draw a PLY file's edges and faces (#8817) (#8820)
* Point clouds: a PLY file's edges and faces as beads and triangles (#5151) A PLY file's `edge` and `face` elements become segments and triangles between the cloud's points (a face as a fan), each with its own properties; a file with them is read whole, since thinning would cut them. A point's numbers vary along the segments and across the triangles that meet there, an element's are constant on it. Segments with `width` and `height` are drawn as beads of that stadium cross-section, meeting mitred where one runs into the next, from one indexed template; without them, as lines. Points no segment or triangle ends on stay dots. A range filter cuts an element where its value crosses an end, on the GPU and in the tracks alike: each element weighs its measure (a dot 1, a segment its length, a triangle its area, each kind over its own total) and spreads it exactly over the values it covers, a segment's evenly and a triangle's as the tent its corners make. Columns saved without the element they are on are on the points, so designs saved with point properties alone still open. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Point clouds: past max_points a PLY is thinned again; the near plane cuts elements exactly A PLY with edges or faces and more vertices than `max_points` was refused, where it used to be thinned. It is thinned again: thinning would cut its edges and faces, so they are left out, with a warning, and raising `max_points` keeps them. A segment or triangle crossing the near plane moved its corners behind the eye to a made-up place, which pulled a wedge across the view. A triangle now keeps its true clip-space corners, which the rasteriser clips exactly. A bead is cut where its axis crosses the plane, a crossing exact because clip-space coordinates are affine along a line, and its numbers are exact there. A ramp accepts MAX_BINS bands but an element was split into 4097, so a ramp finer than that lost measure: half of a segment at 8192. Only the whole numbers have more bands than MAX_BINS. `xtask mesh-decisions` reads any field named `triangles` as a mesh; a cloud's own complex holds none, so its three modules are skipped with that reason. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Point clouds: a ramp's measure is whole past both its ends; a column on the points says nothing A ramp of MAX_BINS bands has one band below it and one above it, so an element running past both ends crosses MAX_BINS + 1 bands past its first. The limit was one short, and such an element lost what lay above the ramp. A column on the points now leaves `on` out when saved, so a design holding only points keeps the form it had, as the field's comment and the pending format note already say. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Point clouds: a set filter keeps part of a bead whose ends differ; an unreadable point takes only what ends on it The set filter's whole-element test read the first corner alone, so a bead whose first end was not kept vanished, while the range tracks counted the part kept. It now drops a bead only when one value at every corner is not kept; otherwise the fragments decide, as for triangles. A PLY with edges or faces and one unreadable vertex was refused whole. It now keeps the subcomplex the readable points span, renumbered, with its numbers, and warns about what it left out. A file with numbers on its points gains the same. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Point clouds: build the triangle corner weights without a dynamic vector write The Windows D3D12 shader compiler rejected w[vi] = 1.0 (error X3500). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: bherbruck <brennen.herbruck@gmail.com> |
||
|
|
ca4f3ed1a0 |
Book: getting started, sheet metal and import/export get pictures (#10732)
* Book: sketching step by step, with three clips and a numbered screenshot The sketching page now opens with a first sketch in four steps: start a sketch on the Top plane, draw a 60 x 40 rectangle and a 12 mm circle with typed values, dimension the circle until the sketch is fully constrained, and finish. Each step has a short clip, and the last a screenshot numbering the Sketch tools, a constraint, a dimension, the sketch's state and Finish Sketch. doc_shots.py gains what these needed: a setup that runs before recording, so a clip starts where the last one ended; sketch framing; Enter sent as two input frames; and clips that keep their pauses (hovering a plane). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Book: the sketching page's general notes get a heading after Step by step Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Book: sketching adds Offset and Trim; the sketching figures again on 0.29.0 Two more clips after the sketching walkthrough: Offset draws the rectangle's outline 4 mm inside it with one click (Chain), and Trim cuts a notch where a circle crosses the top side. All the sketching figures are made again on SolidCraft 0.29.0, with the clips keeping a moment on each result. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Book: solid features step by step, with four clips The solid features page now opens with the sketch from the sketching page made into an open box in four steps, each with a short clip: extrude it 12 mm, shell it with the top open, round its outer top edges, then make it 20 mm tall from the timeline while the shell and the fillet rebuild. The panel table and what follows get a heading of their own. doc_shots.py: the feature shots share their steps with the setups that lead up to the next shot, and fail when a feature on the timeline carries a warning or an error, so no figure shows one. Shell comes before Fillet for that reason: shelling through the rounds needed the kernel's boolean retry. trim_idle.py takes --hold, the seconds of each idle stretch to keep (default 0.1 as before); the doc clips keep 0.8 s, so a reader sees each result. The app gets up to three minutes to answer on a busy machine. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Book: features add Hole and Circular Pattern; the Parameters dialog, numbered The features walkthrough gains two steps before the timeline edit: a 4 mm hole on the box's floor, then Circular Pattern repeating it four times around the tube. The edit at the end now rebuilds all of it. The parameters page gets a screenshot of the Parameters dialog numbering apply as you go, user parameters, model parameters by feature, an expression and its value. The features clips are made again on SolidCraft 0.29.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Book: components and joints step by step, with three clips The components and joints page now opens with a two-leaf hinge in three steps, each with a short clip: the two bodies made into components from the Bodies folder's menu (the first one grounded), a revolute joint on their barrel ends with Flip turning Leaf B the right way round, and a drag that swings Leaf B about the hinge while grounded Leaf A stays put. What follows gets a heading of its own. doc_shots.py builds the leaves from commands, with Leaf B lifted and set back so the joint visibly brings it into place. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Book: assemblies add Drive Joints; the assembly clips again on 0.29.0 A fourth step drives the hinge with Drive Joints: the slider swings Leaf B while a ghost shows where it started, and OK keeps the new angle. The assembly clips are made again on SolidCraft 0.29.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Book: getting started, sheet metal and import/export get pictures Getting started gains a section on the start page: a numbered screenshot (new design, open, import, recent, samples, the File menu) and a clip opening a sample from it. Sheet metal opens with a tray in three steps, each with a clip: a base flange from a sketched rectangle, edge flanges from two top edges, and the flat pattern with its bends. Import and export opens with the File menu, numbered. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
a1d66c238e |
MCP: batch runs the steps of a script file (path) (#5957) (#5959)
Co-authored-by: bherbruck <brennen.herbruck@gmail.com> Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|
|
aae4282f1e |
Polygon: By side shows the Length and Sides boxes (#11271) (#11287)
* claim: #11271 * Polygon By side: Length and Sides boxes, the typed length a side dimension (#11271) The edge polygon tool showed no value boxes after its first click. It now shows Length (the side from the first click) and Sides, as the inscribed and circumscribed modes show Radius and Sides. A typed length places the second corner and becomes a Length dimension on the first side: sketch.draw.dimensioned takes a `length` role for sketch.polygon.edge, an alternative to its radius (as_drawn still adds the radius when no length is given; both together are refused). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Polygon By side test: read the design's own state so it compiles against main (#11271) Main's Session::world_state() now returns a Result, so the new test failed Quick compile on the merge. The sketch is in no component, so the design's own state shows the same sketch on both the old and new bases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Polygon By side test: take Vec2 from solidcore_record, where main moved it (#11271) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: thocsmith <193096300+thocsmith@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
18b698ffa8 |
Keep raised models’ ground shadows on the ground (#9838) (#10257)
* claim: #9838 * fix: anchor raised ground shadows to the origin plane (#9838) * docs: attribute ground shadow preference messages |
||
|
|
051e6236c3 | Regenerate generated files and fold pending files [skip ci] | ||
|
|
8691cefbbf |
Render: save wood images with physical grain controls (#1599)
* Render: save wood images with physical grain controls * Render: prepare plain glass before marking the GPU host ready |
||
|
|
ee1bdea97b | Regenerate generated files and fold pending files [skip ci] | ||
|
|
b916f9bf33 |
Ribbon: an option to fold it to its tab row (#10112) (#10214)
* Ribbon: an option to fold it to its tab row (#10112) Preferences > Layout > "Show only the ribbon's tabs" (off by default), the Ribbon Tabs Only command (view.ribbon_tabs_only), and its settings-profile key. Rebuilt on main's redesigned Layout page. * Ribbon Tabs Only: switching tabs with a panel menu open no longer keeps the overlay open (#10112) A tab click now forgets the open panel drop-down of the previous tab, so the pointer leaving or Escape still closes the overlay. * Ribbon Tabs Only: count its settings-profile key in the profile membership test (#10112) |
||
|
|
733f0b2254 |
MCP: opt-in compact inspect_design and tool output (split from #2901) (#3144)
* MCP: compact inspect_design and tool JSON, off by default (--compact / SOLIDCRAFT_MCP_COMPACT) Split out of #2901 per review: the smaller inspect_design changed the default for everyone, so it is now an MCP server option that is off unless asked for. - solidcraft-cli mcp --compact, or SOLIDCRAFT_MCP_COMPACT=1 (true/yes/on; 0/false/no/off/empty leave it off; anything else is an error at start-up). solidcraft_mcp::Options::resolve is the one place that decides, so an app Preferences setting can feed it later. - With it on, inspect_design summarises sketches (id, name, plane, counts of points, curves, constraints and profiles, dof, status), returns full contents only for the sketches named in `sketches` (names/ids, true, false or "summary"), takes a `bodies` filter and measures only those; unknown names list the existing ones. Tool JSON is compact rather than pretty-printed. - Off, tools/list, argument checks, inspect_design and tool JSON are exactly as before. - document.inspect gains an opt-in `sketch_counts` (plane, points, constraints); without it its reply is unchanged. Tests: both modes in the MCP suite, Options parsing, and the CLI flag and variable end to end. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * MCP compact output: a Preferences setting too (AI › Agents through MCP) The desktop app's Preferences › AI gets "Compact output" under a new "Agents through MCP" section, off by default and shown with the chat off too. The app reports it on the control channel as `mcp.options` ({"compact": bool}); the agent chat lets its own MCP server read it. A bridged MCP server (`solidcraft-cli mcp --connect`) asks the app when an agent first lists or calls a tool and keeps the answer for the session, so the tools it listed keep their shape. An app not running yet, or busy past 2 s, is asked again on the next call; an app from before the setting counts as off. `--compact` and SOLIDCRAFT_MCP_COMPACT=1 still turn it on whatever the app says. Tests: the server follows the app's answer (waits for it, keeps it, the flag still wins); the checkbox reaches `mcp.options` and Restore Defaults clears it; the chat gate allows `mcp.options`. docs/mcp.md and docs/control-protocol.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * MCP compact output: review fixes (mcp.options never blocks, headless test, locales, prefs doc) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * MCP compact output: the setting is a section of the AI page; the bridged test answers mcp.options Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * MCP compact output: the preference test sets it through ui.prefs; rustfmt Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * MCP compact output: look for a newly started app before asking its options; counts from sketch.inspect for an older app Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
d92923a964 | Agent chat: a Cheaper Inference preset for OpenAI-compatible endpoints (#11174) | ||
|
|
71598c0354 |
Agent control: ui.menu refuses items the design doesn't have, reports the History bar's right-click menu, and gives Edit Joint Limits its own id (#10745) (#10746)
* claim: #10745 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Control channel: ui.menu refuses missing targets, reports the History item menu, and tells the joint menu items apart (#10745) - ui.menu looks a target up and refuses one the design doesn't have ("no body `NoSuchBody`"). - The History bar's feature menu is the shared context menu (Target::Timeline), so ui.menu reports it, ui.menuPick runs its items and {"type":"timeline","feature":id} opens it. Its Show All toggle moves to TreeState so the menu can list Delete after the marker. - Edit Joint Limits is ui.editJointLimits and opens Edit Joint with Limits expanded. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Icon audit: open the section and canvas menus on a real section and canvas; a hidden section has a menu too Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ui.menu: check a group's or folder's scope and folder name; Delete after the marker gets its own id A group or folder target is refused unless its scope is a row of its component (`c<id>` or a placement of it) and the folder is bodies, sketches or construction. The History item menu's delete of everything after the marker is ui.deleteAfterMarker, so ui.menuPick can tell it from Delete (review on #10746). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ui.menu: a component's own c<id> scope is the design root's only; test that Delete after the marker deletes The browser draws a part's folders and groups under its placements (o:<path>), so a c<id> scope for any component but the root names a row that isn't there (review on #10746). The History test now picks ui.deleteAfterMarker and checks the features are gone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ui.menu: a placement scope must be spelt as the browser keys it o:012 parses to placement 12 but isn't the row's key (o:12), so Show/Hide would store a key no row reads (review on #10746). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * History item menu: no Delete after the marker when nothing shown is after it A timeline target for a feature the bar's component filter leaves out listed no features, so the item did nothing (review on #10746). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ui.menu: a plane target must be construction geometry The plane menu's Show/Hide keys the feature's name as an origin item, so any other feature got a menu whose actions don't fit it (review on #10746). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * ui.menu: accept the view navigator's and selection filter's menus, which main added Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
4d2691e636 |
Assistant: opt-in HTTP authentication for private endpoints (#5341) (#10674)
* claim: #5341 * Allow per-endpoint HTTP authentication with explicit consent * fix: discard model listings after HTTP consent revocation |
||
|
|
6b5c5dc6e8 |
Sketch on a thickened surface's face (#7641) (#7703)
* claim: #7641 * Sketch on a thickened surface follows the face (#7641) Thicken dropped the kernel's face history, so Create Sketch refused every face of the solid. Carry that history through, the same way Shell and Trim do. The regression covers the offset face and an end wall, and checks that a boss on the offset face follows a thickness change and reopens. |
||
|
|
7c89f7445f |
Assembly: moving a component without capturing its position marks the design unsaved (#9736) (#9851)
* Claim #9736 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Assembly: a move not captured yet is an unsaved change (#9736) A component moved without capturing its position left the design reading as saved: file.save wrote the file without the move and said nothing, and closing the tab didn't ask. Now: - Session::is_dirty is true while a move is pending, so closing a tab or quitting asks "save changes?". - file.save and file.save_as refuse while a move is pending, naming the component and the capture and revert commands. - In the app, Save As (and Save As JSON, Save a copy, Download design) asks the Capture Position question first, as Save already did; a tab closing after "Save" waits for that answer, and Cancel keeps it open. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Close: the save-changes card waits behind the Capture Position question (#9736) Saving a tab that closes asks the Capture Position question first; the "save changes?" card stayed drawn over it and took a second answer. It now hides and ignores answers until the question is answered. The design container doc says a save stops for a move not captured. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Assembly: an exploded view shown is not a move to save (#9736) explode.show displays a view through the pending moves, as an uncaptured move does. Those placements last only while the view is shown, so they don't make the design unsaved and don't stop a save (Session::moved_uncaptured). A move on top of a shown view still does. The relink test saved with a move pending; it captures it first now. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Assembly: the pending-move save test reads the world state as main now gives it world_state() returns a Result since the kernel merge; the test unwraps it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com> |
||
|
|
26adcfa997 |
Docs: add BoxInsertDesigner to the showcase (#10095)
* Docs: add BoxInsertDesigner to the showcase Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Docs: attribution rows for the BoxInsertDesigner showcase recording Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
4a906699ee |
Browser: the component menu keeps its everyday actions and groups the rest in flyouts (#8769) (#8770)
* Browser: the component menu keeps its everyday actions and groups the rest in flyouts A component's or placement's right-click menu had grown to about thirty entries in seven blocks. Activate, Edit in Place, Open Linked Design, Move/Copy, Show/Hide, Isolate, the clipboard, Delete, Rename, Appearance, Physical Material and Properties stay on the menu; Ground, Capture and Revert Position, Unlock Contents and Turn Up Axis move to a Position flyout, Relink Source or Extract to File and the exports to File, New Component, New Group and Paste New to New, and Show All Bodies, Cycle Component Color, Expand All and Collapse All to Display. context_menu::entries lists a menu with its flyouts, as ui.menuPick reads it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: the component menu nests its flyouts by topic, and flyouts no longer scroll Position (Ground, Capture and Revert Position, Unlock Contents, Turn Up Axis), Component (New Component, Rename, Appearance, Physical Material, Cycle Component Color, Relink Source or Extract to File, Properties; Design on the design's row), Export (Export, Save As Mesh, Send to Slicer) and Browser (New Group, Expand All, Collapse All) each open a flyout; Paste New stays with the clipboard and Show All Bodies with Show/Hide. Flyouts open inside flyouts, so Appearance keeps its quick choices inside Component; the keys walk in and out of them. A flyout no longer scrolls or sits away from its row: every flyout has its own area, measured whole, where a short one used to squeeze every later one into its height. A component's only body is no longer offered as a component of its own on a folded Bodies folder's entries. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: the component menu starts with what a double-click does, and keeps the old order of its sections A linked component's menu starts with Edit in Place and Open Linked Design when a double-click edits it in place (double_click_components), and with Activate otherwise. Position, Component and Export follow Move/Copy, then the clipboard, then Show/Hide and Isolate, with Browser last, as the sections came before the flyouts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: Show All Bodies is on a component's menu only while a body is hidden It is listed while a body is hidden itself, in a hidden placement, or in a hidden Bodies folder or group of bodies, anywhere in the design, since that is what it shows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: Relink Source and Extract to File sit right below Rename in the Component flyout Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: Placement and Organize flyouts, Turn Up Axis back as a flyout, and flyout fixes Placement (Ground, Turn Up Axis, Capture and Revert Position, Unlock Contents) follows Move/Copy above the first separator, Turn Up Axis opens its two turns in a flyout again, and the Browser flyout is called Organize. The Component flyout has three blocks: New Component with Relink Source or Extract to File, then Appearance, Physical Material and Cycle Component Color, then Rename and Properties. A flyout of a flyout that opened to the left opens to the left too instead of covering the menu, Left back to the menu chooses the row that opened the flyout, ui.menuPick refuses a row that only opens a flyout, and the icon audit checks every level. The guides and the control protocol describe the new menu paths. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: ui.menu gives a flyout's rows their placeholder flag too ui.menu set placeholder only on the top-level rows, so a client reading a flyout row's placeholder got nothing. The icon audit now reads the flag of the flyout rows instead of resolving their icons itself. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
af5644aee6 |
Ribbon: switch panel menus on hover after the first click (#11447) (#11713)
* claim: #11447 * Add an option to switch ribbon panel menus on hover * Update profile membership count for ribbon hover setting |
||
|
|
5ab59e7c1b |
Assistant: DeepSeek and Qwen endpoint presets (#5016) (#5063)
Adds DeepSeek and Qwen presets to both endpoint protocols: OpenAI-compatible (api.deepseek.com, dashscope-intl compatible-mode/v1) and Anthropic-compatible (api.deepseek.com/anthropic, dashscope-intl apps/anthropic). Co-authored-by: Claude Code <noreply@anthropic.com> |
||
|
|
08fa042039 |
Dialogs: drag a value's label sideways to change it (#2217) (#9685)
* claim: #2217 * Dialogs: drag a value's label sideways to change it (#2217) A value row's label (expr_row, hint_row) now scrubs a literal value: about a hundredth of its size per point of drag, on that step's grid, Shift ten times finer, Ctrl/Cmd ten times coarser. The unit and decimal mark stay as typed, a size never turns negative, and expressions and parameters are left alone. The text changes as if typed, so previews follow and OK still makes one command. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Label drag: measure from the press point, cap values, keep scrub kit-private Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
46edd8d749 |
Agent chat: Custom instructions in Preferences, added to the system note (#8220) (#11105)
* claim: #8220 * Agent chat: Custom instructions in Preferences, added to the system note (#8220) Preferences > AI gets a multi-line Custom instructions field, saved with the other AI preferences (agent_instructions, kept by page resets like other user-written text). The chat adds the text after its own system note when a session starts, by the routes #9811 set up: ACP session/new (the Claude adapter's _meta key, the standard systemPrompt field, the Antigravity key) and the system message or field of every API protocol. Connect and New chat set it, so an edit applies from the next chat and never changes the one running. Blank text adds nothing; at most 4000 characters are kept, in the field, over ui.agent_chat and from a hand- edited settings file. ui.agent_chat takes and reports `instructions`. * Custom instructions: typing in the field stays in the field The text area did not report itself to Preferences search as a key sink, so with the field focused, search took the typed characters and moved focus away. The field now notes the sink while it has focus, like the other preference fields, and the #8220 test types into it. --------- Co-authored-by: MateuszSychXpl <151755914+MateuszSychXpl@users.noreply.github.com> |
||
|
|
c4a63a1d43 |
GPU path tracer: don't rerun a setup that crashed in the driver (#9236) (#9666)
* claim: #9236 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * GPU path tracer: don't rerun a setup that crashed in the driver (#9236) A driver that takes the process down while it compiles the path tracer (RADV on an RX 7600) is beyond error scopes and unwind guards. A running setup now keeps gpu-path-setup.json (its adapter key) in the settings folder, removed when the setup answers or the app closes normally. A launch that finds it for the same adapter leaves the setup failed with an explanation and a Try again button; CPU ray tracing stays available, and a driver update changes the key and so tries again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
2fdcc5ae49 |
Appearance: a picture of your own behind the model (#11353)
* Appearance: a picture of your own behind the model Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Background picture: a label that fits its row Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
d9421bf2ca |
Browser: an option to start folders closed and open rows only on request (#8768) (#8771)
* claim: #8768 * feat: Browser folders start closed and find a body only when asked, behind a preference Preferences › Layout › Browser rows start closed (`browser_rows_start_closed`, off by default) starts the Browser's folders closed, and placements too whatever "Components start open" (#9274) says. Rows then open with their arrow, Expand All or Find in Browser, which opens just the rows down to its body and closes again the ones the last find opened. A body picked in the 3D view leaves the Browser as it is, and only the body Find in Browser found has the rows above it marked, so a large assembly's placements are not named again after each edit. With the preference off, folders start open, placements start as "Components start open" says, and a pick in the 3D view opens the Browser down to its body, as on main. Find in Browser looks the body's placement up once and opens its rows before drawing, instead of each row testing the revealed path while it is drawn. * Browser tests: read the row order from the Browser's content frame Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: bherbruck <brennen.herbruck@gmail.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
774c45a512 |
Dynamics: rigid-body solver core with joints, gravity and springs (#9719) (#9721)
* claim: #9719 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Dynamics: rigid-body solver core with joints, gravity and springs (#9719) A new L1 crate, solidcraft-dynamics (geom only): rigid bodies in maximal coordinates, joint constraint equations with analytic Jacobians for rigid, revolute, slider, cylindrical, planar and ball joints, gravity, linear spring-dampers and constant loads; the index-1 equations of motion solved through a rank-revealing Schur complement (repeated joint equations are solved, not refused); RK4 and Dormand-Prince 5(4) with position and velocity projection; joint values, rates, reactions and energies at every output sample; caps on bodies, joints, rows, steps and samples; Result errors only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Dynamics: take Vec3 from the record crate after the layer split, refresh the lock file Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: bherbruck <brennen.herbruck@gmail.com> |
||
|
|
3aee35fe01 |
Web app: keep unsaved work in the browser instead of the leave-page box (#10220) (#10221)
* claim: #10220 * Web app: keep unsaved work in the browser instead of the leave-page box (#10220) A new preference, off by default, on Preferences > General > Saving (web app only): "Keep unsaved work in this browser instead of asking when the tab closes". With it on, each open design with unsaved changes keeps a copy in the browser's private storage (keep-<page>-<design>.sc/.json), written once the design has been still for 0.8 s (at most 4 s after the first change it lacks) and again on pagehide or when the page is hidden. While every copy is current, beforeunload doesn't ask. A copy goes when its design is saved, closed, or the preference is turned off. The next visit offers the copies newer than their design's last save in SolidCraft's own window, "Restore unsaved design: <name>, changed <time>?", one window for several, with Restore, Open saved version, and Discard. A page holds a Web Lock while it runs, so another open tab's copies are never offered or removed. With the preference off, the single autosave and the browser's prompt work exactly as before. * Web app: the restore window comes from the UI kit's recovery module (#10220) The kit's text and divider helpers are private to the UI crate, so the "Restore unsaved design?" window moves to recovery_ui (browser_copies_window), beside the desktop recovery window, and the web shell only maps its answer. Also keeps the window handle for the page listeners instead of using the one moved into the app. * Web app: restore window buttons sit in one row (#10220) * Web app: keep unsaved work and still ask, unless told not to (#10220) Keeping a copy in the browser no longer replaces the browser's leave-page box by itself. A second option, shown once work is kept and on by default, leaves the box in place; off, the box appears only while a copy isn't current. * Web app: kept-copy review fixes (#10220) A failed write of a kept copy waits 30 s before the next try, a recovery copy is dropped only after the remembered saved file has opened, the preference is documented under its current label, and the ui.prefs list is sorted again. |
||
|
|
5562d9c6c8 |
Quick-access bar: pin ribbon commands to the application bar (#10223) (#10224)
* claim: #10223 * Quick-access bar: pin ribbon commands to the application bar (#10223) A command's menu (a ribbon button, a section drop-down row or a command search result) has Add to Quick Access: the command's own icon joins the application bar after Save, Undo and Redo. A click starts it as its ribbon button does, a drag along the bar reorders the buttons, and the button's menu has Remove from Quick Access. Empty, and so not drawn, by default; it holds up to 24 commands. The list is kept with the toolbar's customisations (`quick_access` in the toolbar's saved document), so it is saved, exported with the keyboard shortcuts and carried by settings profiles. * Quick access: a pinned family variant no longer replaces the ribbon choice A quick-access click now starts the pinned command with start_pinned, so it starts exactly that command and leaves the sketch family remembered choice (the main ribbon button) unchanged. |
||
|
|
0690ee5875 |
Web app: run as a modelling editor inside another page that keeps the design files (#8517) (#11273)
* claim: #8517 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * web: editing embed for host pages (?embed=editor, #8517) A host page that keeps the files itself and frames SolidCraft for modelling needs the modelling UI without the application chrome. `?embed=editor` runs the web app as such an embed: - no application bar (logo, File menu, document tabs, update, help, report a bug) and no start page; the layout is docked; - the ribbon, browser, timeline and properties stay; Ctrl+Z and Ctrl+Y still undo and redo; - Ctrl+N, Ctrl+O, Ctrl+S, Ctrl+W and Ctrl+, are left to the host; - nothing is kept in the browser (no stored designs, autosave, recovery prompt, preferences or leave-page prompt), as with the existing viewer embed. The existing `?embed&open=` viewer embed is unchanged. SolveApp gets one flag, `embed_editor`, for desktop and test hosts too. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * control: document.export / document.import / document.saved for a host (#8517) An editing embed's host keeps the design itself. Three control methods (window.solidcraft.request in the browser; the desktop control channel too; not the agent chat's, whose method list is unchanged): - `document.export` -> {name, revision, dirty, format: "json", text}: the active design as a `.json` design file holds it. `revision` is the one `document.revision` answers, so a host that follows the design compares one number. - `document.import {text, name?}`: replaces the active design with that text, timeline and parameters as saved, opened saved with a new `document_id`. It runs as a design opened in a tab of its own, with the old tab closed without asking, so whatever was open in the old design leaves with it. A text that does not read leaves the design as it was. Waits behind a file loading or a design change, as commands do, and evaluates on the window thread. - `document.saved {revision}`: the host saved that revision; refused when the design has changed since. They are control methods, not commands: they act on the app's open design. The browser API test gets a round trip through all three. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: aduijs <7501203+aduijs@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
1dd921fc52 |
Components: stop Capture All Positions from doubling moves (#11259) (#11364)
* Model cache: a body made by rounds keeps them, so a later round blends them the same after opening A design gave another body when opened from its model cache: the rounds a body was made of lived only in memory, so a later round at their mitre was built sequentially (or refused, as too large) after opening and blended with them when evaluated anew. The saved model now records, per kernel body made by rounds, the body they were made on (a place in the bodies, stored once though no state holds it) and the edges with their radii; reading it attaches them back down each chain, and a thinned model keeps those bodies with the bodies made from them. Model cache format 7. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: a corner patch of rounds 2/3/4 takes no more than the strips leave in its block three_rounds_at_a_corner bounded the patch's extra cut at 3 mm³ beyond the strips, a figure with no derivation; SMLib's all-at-once body at radii 2, 3, 4 takes 3.099 (V 7878.579574 against strips 7881.678). That body is the strips' outside the block its patch lies in: its rounds are the strips' cylinders ending at a's section y = rc, b's x = 20 − rc and c's rails where they meet a's and b's (the patch's four corners, now asserted), so the patch takes at most what the strips leave in that block (11.86 at 2/2/3, 32.69 at 2/3/4). The lower bound is that block; the upper one, at most the strips' volume, stays. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Tests: the io crate's hand-built saved models list their rounds, as format 7 records do Model cache format 7 ( |
||
|
|
51d237829a | Regenerate generated files and fold pending files [skip ci] | ||
|
|
ef2f485e15 |
Extend viewport AO to the existing virtual ground (#3413) (#11979)
* claim: #3413 * feat(gpu): extend viewport AO to the virtual ground * test(gpu): retain measured AO render attachments * perf: initialize ground AO pipeline with concurrent jobs * fix(gpu): size ground AO receiver for the current frame radius * fix(viewport): retain orbit caches when ground AO visibility changes |
||
|
|
f8a98eed33 | Regenerate generated files and fold pending files [skip ci] | ||
|
|
1432131e95 |
English: command labels in title case, other labels in sentence case (#9085) (#10734)
* English: command labels in title case, other labels in sentence case (#9085) The rest of #9085 after #9194 (the plural and the spelling) and #9907 (the Preferences page names). Command labels are in title case (422 of 430 were already); the seven in sentence case follow, and Fix/UnFix reads Fix/Unfix. The UI text skill states the rule. The user docs name the Preferences footer's button by its current label, Restore page defaults (#10295). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Navigation bar menu test: the echo names the command by its own label Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * UI text skill: state the case rule in one short sentence, under the 3600 limit Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Localization doc: the case rule in full, with examples Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Localization doc: the example button is Restore page defaults now Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
06def2231d |
Agent chat: tell the agent the design changed by hand since its last reply (#10854) (#11144)
* claim: #10854 * Agent chat: tell the agent the design changed by hand since its last reply (#10854) The chat remembers the design as the agent last saw it, at the end of a turn it answered or worked in. When the next message goes and the design is no longer that one, a note goes before the message for the agent (not into the conversation, like the note after an interruption): the user changed the design by hand, which parameters changed from what to what, which features are new, edited or removed, where the History marker went, and to read the design again before reusing positions, picks or sizes. A new chat and a stopped backend forget it, so a session that has seen nothing gets no note. Each list names at most 12 items and counts the rest; names and expressions are cut at 60 characters. * Agent chat docs: the design-changed note asks the agent to read the design again (#10854) --------- Co-authored-by: MateuszSychXpl <151755914+MateuszSychXpl@users.noreply.github.com> |
||
|
|
d39fd6c397 |
Assistant: discover Mistral Vibe and offer sign-in (#11692) (#11704)
* claim: #11692 * Assistant: discover Mistral Vibe and support its sign-in (#11692) |
||
|
|
91ecea8cfd |
Properties: account for sheet perforations (#6025) (#6028)
* claim: #6025 * fix(engine): account for sheet perforations in physical properties * fix(inspect): retain kernel topology counts for sheet bodies |
||
|
|
8068e8f4b8 |
Preferences: the theme strip's arrows page by a screenful of themes (#11434) (#11600)
* claim: #11434 Signed-off-by: Maurizio Monticelli <maurizio@whatwedo.ch> * Preferences: the theme arrows move by the themes that fit in view The previous and next arrows beside the theme cards in Preferences > Appearance moved the row by one card per click, although their hover text says "Previous themes" and "Next themes". With 26 themes and about six cards in view, reaching the last theme took some twenty clicks. The shared carousel now moves by the number of cards that fit at the current width, so one click shows the next screenful. The last page ends on the last card, the first page starts on the first, and the arrow at an end stays dimmed and inert. The step follows the window width, and the row still opens on the chosen theme. Fixes #11434 Signed-off-by: Maurizio Monticelli <maurizio@whatwedo.ch> --------- Signed-off-by: Maurizio Monticelli <maurizio@whatwedo.ch> |
||
|
|
e27d17c421 |
Assistant: offer the Mistral AI endpoint in Add Agent (#11246) (#11715)
* claim: #11246 * Assistant: offer the Mistral AI API endpoint (#11246) |
||
|
|
de9a2bc846 |
Shaded with hidden edges: optionally select edges through faces (#11841)
* Allow optional hidden-edge picking in Shaded with hidden edges Keep visible-only picking as the default. Cover the preference, hover cache, section and body visibility, and Fillet inputs in the existing UI tests. Use platform-absolute fixture paths in the Windows CI argument-parser test. * Respect section caps and visible-edge ties in hidden-edge picking * Keep section caps as occluders behind nearer kept faces |