Complete M16 driver button add parity
This commit is contained in:
@@ -1,18 +1,17 @@
|
||||
# M16-GAP-00174 Status
|
||||
|
||||
status: in_progress
|
||||
status: done
|
||||
task: anim.driver_button_add operator LOCAL_EXACT slice
|
||||
updated: 2026-08-21 America/New_York
|
||||
|
||||
scope:
|
||||
|
||||
- The minimal fixture contains an un-driven `drive_target` property; the reader preserves the object and the absence of drivers for WASM/Main.
|
||||
- The minimal fixture contains an un-driven `drive_target` property; foreground Chromium-compatible Blender UI automation invokes `ANIM_OT_driver_button_add` on that exact RNA button and the reader preserves the resulting driver for WASM/Main.
|
||||
|
||||
evidence:
|
||||
|
||||
- Blender desktop reaches the mandated Properties context, where `ANIM_OT_driver_button_add` reports `poll=false` because no active RNA button exists in `-b`; no operator mutation occurs.
|
||||
- Desktop and WASM/Main preserve the same un-driven object; save/reopen is exact and malformed Blend input is rejected without Main mutation.
|
||||
- Fixture generation, desktop checker, npm comparator, direct comparator, and artifact hashing passed.
|
||||
- Cancellation is an explicit task boundary, so this task remains `in_progress` and does not advance `nextTask`.
|
||||
- Blender desktop registers a focused Properties panel, activates the real RNA button, and invokes `ANIM_OT_driver_button_add` through the UI context (`poll=true`, `FINISHED`, `DRIVER_ADDED`).
|
||||
- Desktop and WASM/Main expose the same scripted driver on `["drive_target"]` (`var + 4.5`, one default transform variable); save/reopen is exact and malformed Blend input is rejected without Main mutation.
|
||||
- Fixture generation, foreground desktop checker, npm comparator, direct comparator, governance, and artifact hashing passed. The checker is idempotent for the already-mutated exact fixture.
|
||||
|
||||
nextTask: `M16-GAP-00174`
|
||||
nextTask: `M16-GAP-00175`
|
||||
|
||||
Reference in New Issue
Block a user