8564006ffb81679fc8aa55a9de0bd4d76431aac4
3
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
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> |
||
|
|
332f96c26a |
Point clouds: colour and filter by any property the file carries (#8816) (#8819)
* Point clouds: colour and filter by any property of a PLY file, on range tracks (#5151) A PLY file's other vertex properties are kept as named numbers on the points (whole-numbered for integer types; a comment `property: 0 name, 1 name` names a label's values). A cloud is coloured by any of them, a ramp or a palette for whole numbers, and filtered by up to eight, each a range or a set of named values. The GPU colours and filters the points itself, so editing a range uploads nothing. In the Edit Point Cloud card each range is a track, as in an audio editor: a histogram of the property over what the other filters keep, stacked by colour, under an overview strip. Ranges are drawn, moved, snapped to colour changes, typed (Start, End, Length, relative values) and played (Space or Play). The automatic colour range is exactly the values the property takes over what the filters keep. pointcloud.insert and pointcloud.edit take color_by: <property>, color_range and filters; pointcloud.list reports them with the properties. docs/point-clouds.md describes it all. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Point clouds: note the saved properties, colouring and filters as a pending format change (#8816) A design now saves a cloud's per-point columns and their value names, colouring by a property and filters; an older release must refuse it instead of dropping them. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> |
||
|
|
e6dc105134 |
Point clouds: insert PLY, XYZ and PTS scans as a modelling reference (#5151) (#5381)
* Point clouds: insert PLY, XYZ and PTS scans as a modelling reference (#5151) A point cloud is kept in the design as a reference, drawn as depth-tested dots and never a body. - io: a PLY reader (ASCII, binary little/big endian; x, y, z of any numeric type, optional colours, other elements skipped; counts checked against the file) and XYZ/PTS text, thinned evenly past max_points. PLY meshes with faces can also come in through file.insert_mesh. - doc: Document.point_clouds (shared f32 points relative to an f64 origin, colours, units, rigid placement, size and colour), stored as a binary container part; format change in pending/point-clouds.rs. - engine: pointcloud.insert / edit / delete / list; doc.open opens a cloud as a new design; selection.delete takes point_clouds; view bounds include them. - gpu: an instanced point-sprite pipeline (16 bytes a point). - ui: Browser Point Clouds folder with eyes, menu and an Edit Point Cloud card; drop, Open, Insert and file dialogs take .ply/.xyz/.pts; a CPU viewport fallback; messages in en, en-GB, ja, zh, de and ko. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Point clouds: colour by the file, one colour or height, from the UI (#5151) The Edit Point Cloud card gets Color By (File Colors, Single Color, Height). Height is a blue-to-red ramp over design Z, between the cloud's own two heights or, by default, a range worked out from the points (all but the lowest and highest 2 %, from an even sample). pointcloud.insert and pointcloud.edit take color_by and height_range; pointcloud.list reports them. The colour of each point is worked out in one place (PointCloud::shade) for the GPU and CPU viewports. Also: the card's dropdowns compare the picked index (a dropdown's response doesn't report the pick, so File Units did not change either). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Point clouds: integrate format registration and viewport caches (#5151) * Point clouds: satisfy current UI audits and document comparisons (#5151) Route model RGB data through the theme conversion boundary, provide a compact ribbon label, and include point clouds in the new document comparison. Gate the Unix-only CLI-link helper and test so Windows all-target checks remain buildable after the rebase. * Point clouds: isolate translations for current main (#5151) Move the existing 74 messages unchanged into one pending locale file and attribute it through a pending row, following the current repository workflow. Repository checks, 50 tooling tests, final workspace Clippy, wasm and generated-catalog equality checks passed after the rebase. * Point clouds: fit the rebased code to main's GpuTarget and Frame Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Compare point clouds when reusing placement-independent results Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Point clouds: complete command help and required translations (#5151) * Point clouds: size the save cap from the raised limit after the rebase 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> |