Ryan Schultz 6ca69d20d9 dev-notes: record the material usage trap in should_map_representations ...

The note under "assign_type preserves per-instance" carried a caveat that
skipping the mapping also keeps the occurrence's own profile/material, "fine
when all types share one profile -- revisit if reassigning across different
profiles". That is exactly what bit: map_material_usages lives inside the same
if-block, so the occurrence kept a usage pointing at the old type's profile set
and the material panel edited the old type.

Replace the caveat with what actually happens, why the fix reuses
material.assign_material rather than setting ForProfileSet by hand, and where
the coverage lives. Tick the matching checklist item.

Generated with the assistance of an AI coding tool.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-07-30 21:37:34 -05:00

..

cpp-api

apply cmake file formatting

2026-01-26 17:10:03 +05:00

dev-notes

dev-notes: record the material usage trap in should_map_representations

2026-07-30 21:37:34 -05:00

conf.py

Sort imports

2025-12-19 18:53:14 +05:00

contents.rst

Changes to docs

2021-02-05 12:01:57 +00:00

generate_docs.py

Sort imports

2025-12-19 18:53:14 +05:00

index.rst

Documentation changes

2021-02-06 15:10:41 +00:00