jyvikoandClaude Opus 5.5
177eb207fe
explode.show put the view's placements in the uncaptured moves, so occurrence.properties reported
the exploded placement and Capture Position (and reparenting, moving bodies between components,
copying or pasting in place, URDF export) wrote the view's offsets into the design. The session
now records which uncaptured moves are the view's (Session::exploded); what reports the design's
placements or works a new placement out from them uses the design's own moves
(uncaptured_moves, design_document), while the viewport and picks still show the view.
New case cov-explode-show-keeps-the-placements: the arm's properties are the same before, while
and after the view is shown, and Capture Position keeps nothing. The two explode cases that read
occurrence.properties while exploded now expect the design's placement, centre (20, 0, 5), as the
command says ("shown only; the design keeps its placements").
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
43 lines
902 B
JSON
43 lines
902 B
JSON
{
|
|
"sources": [],
|
|
"what": "an automatic exploded view of scale 2",
|
|
"source": "analytic",
|
|
"method": "Base: box 20x20x10 from (-10,-10,-10), grounded; Arm: box 40x10x10 from (0,-5,0), centre (20,0,5); each occurrence moves scale \u00d7 (its centre - the mean of the centres): centres (0,0,-5) and (20,0,5), mean (10,0,0): Base by (-20,0,-10), Arm by (20,0,10); shown only (the design keeps its placements), so occurrence.properties reports Arm where the design places it: centre (20,0,5)",
|
|
"body_count": 2,
|
|
"volume_mm3": 8000.0,
|
|
"results": [
|
|
{
|
|
"step": 8,
|
|
"json": {
|
|
"moves": [
|
|
{
|
|
"translate": [
|
|
-20.0,
|
|
0.0,
|
|
-10.0
|
|
]
|
|
},
|
|
{
|
|
"translate": [
|
|
20.0,
|
|
0.0,
|
|
10.0
|
|
]
|
|
}
|
|
]
|
|
}
|
|
},
|
|
{
|
|
"step": 10,
|
|
"json": {
|
|
"total": {
|
|
"center_of_mass": [
|
|
20.0,
|
|
0.0,
|
|
5.0
|
|
]
|
|
}
|
|
}
|
|
}
|
|
]
|
|
} |