three-slicer 0.2.0 → 0.2.1

package/README.md

@@ -436,7 +436,6 @@ not cover fails with a stable error instead of silently producing something else
 | --- | --- |
 | `SLA_UNSUPPORTED_HOLLOWING` | `hollowing_enable` or drain holes — a solid slice answered to a hollow request would be a mislabeled print |
 | `SLA_UNSUPPORTED_ORGANIC` | organic support trees |
-| `SLA_PAD_AROUND_OBJECT_UNSUPPORTED` | zero-elevation pad embedding (`pad_around_object`) |
 
 `SLA_CAPABILITIES` (exported from `three-slicer/client`) is the machine-readable capability map. A `.3mf`
 carrying SLA records survives round-trip regardless: manual support points and drain holes are preserved on

package/engine/README.md

@@ -358,7 +358,7 @@ Results carry the split: `stats.filament_mm_by_tool` (indexed by tool number, on
 ## SLA parameters
 
 The table above is the FFF kernel's reader. The SLA entry (`slice_sla`) reads its own parameter set, produced
-by `deriveSlaParams(settings)` — unlike `deriveKernelParams` it always emits every key (49 today), filling
+by `deriveSlaParams(settings)` — unlike `deriveKernelParams` it always emits every key (54 today), filling
 schema/reference-machine defaults, because the SLA keys are not shared with another technology whose defaults
 could disagree. The groups:
 
@@ -368,7 +368,7 @@ could disagree. The groups:
 | Display (doubles as the bed) | `display_width/height`, `display_pixels_x/y`, `display_orientation` (portrait default), `display_mirror_x/y`, `bed_width/depth` |
 | Archive identity (config.ini) | `printer_model`, `printer_variant`, `printer_settings_id`, `sla_print_settings_id`, `sla_material_settings_id`, `material_print_speed` |
 | Supports (upstream `SupportTreeConfig`) | `supports_enable`, `support_tree_type`, `support_pillar_diameter`, `support_head_*`, `support_points_density_relative`, `support_critical_angle`, `support_max_bridge_length`, `support_max_pillar_link_distance`, `support_base_*`, `support_small_pillar_diameter_percent`, `support_pillar_widening_factor`, `support_max_bridges_on_pillar`, `support_max_weight_on_model`, `support_object_elevation`, `support_pillar_connection_mode`, `support_buildplate_only`, `slice_closing_radius` |
-| Pad (upstream `PadConfig`) | `pad_enable`, `pad_brim_size`, `pad_wall_thickness`, `pad_wall_height`, `pad_wall_slope`, `pad_max_merge_distance`, `pad_around_object` (typed error) |
+| Pad (upstream `PadConfig`) | `pad_enable`, `pad_brim_size`, `pad_wall_thickness`, `pad_wall_height`, `pad_wall_slope`, `pad_max_merge_distance`, `pad_around_object` (embed — forces zero elevation), `pad_around_object_everywhere`, `pad_object_gap`, `pad_object_connector_width/stride/penetration` |
 | Capability gate | `hollowing_enable` — `true` is refused with `SLA_UNSUPPORTED_HOLLOWING`, never sliced solid |
 
 The result has no G-code: `stats.sla` is `true`, layers carry the same stride-8 segment stream, `support_mesh`

package/engine/src/settings.js

@@ -688,6 +688,13 @@ export function deriveSlaParams(settings) {
     pad_wall_slope: num('pad_wall_slope', 90),
     pad_max_merge_distance: num('pad_max_merge_distance', 50),
     pad_around_object: !!settingRaw(settings, 'pad_around_object'),
+    // Embed mode (upstream PadConfig::EmbedObject): the ring's gap and the connector sticks that keep the
+    //  object attached to the pad. Read even when embed is off — the kernel ignores them then.
+    pad_around_object_everywhere: !!settingRaw(settings, 'pad_around_object_everywhere'),
+    pad_object_gap: num('pad_object_gap', 1),
+    pad_object_connector_width: num('pad_object_connector_width', 0.5),
+    pad_object_connector_stride: num('pad_object_connector_stride', 10),
+    pad_object_connector_penetration: num('pad_object_connector_penetration', 0.3),
   }
 }
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "three-slicer",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "description": "Browser/WASM 3D-printing slicer reverse-engineered from OrcaSlicer: slicing engine (Arachne walls, tree/grid supports, multi-material), SLA resin slicing with PrusaSlicer's ported support/pad chain and .sl1 export, React viewer with GPU toolpath preview, and schema-driven settings UI.",
   "license": "AGPL-3.0-or-later",
   "type": "module",

package/viewer/README.md

@@ -68,8 +68,8 @@ Every panel can be switched off, and the values the component owns can be seeded
   `printer_technology` says SLA swaps the filament card (and the prime tower, and the painting brushes) for the
   resin card, and slicing routes to the kernel's `slice_sla` — PrusaSlicer's ported support/pad chain — with an
   `.sl1` export instead of G-code (portrait masks, like every SL1-family machine). The preview lifts the model by
-  `stats.lift_layers` (pad + elevation), and a request the port does not cover (hollowing, organic trees,
-  `pad_around_object`) surfaces as a typed error instead of a wrong print.
+  `stats.lift_layers` (pad + elevation), and a request the port does not cover (hollowing, organic trees)
+  surfaces as a typed error instead of a wrong print.
 - **`gcode`** — G-code text drawn on the selected plate instead of a slice result. `parseGcode` recovers roles from
   `;TYPE:` (OrcaSlicer/PrusaSlicer/Cura), from `;_EXTRUSION_ROLE:` tags and from this kernel's own feature comments;
   bead width comes from `;WIDTH:` or, absent that, from E. What the file never states cannot be recovered: an