Blend: the setEasing docs list the easing types and say when a blend made without a spine takes easing

docs/mcp.md lists the four easingType values. It and the
object.blend.setEasing params text say that a blend made without a
spine takes easingType and ramp once Replace Spine has given it one,
which the set_easing test now checks.
This commit is contained in:
dotCooCoo
2026-11-12 06:00:56 -08:00
parent 448685b2d7
commit a0902005f7
3 changed files with 11 additions and 4 deletions
+4 -3
View File
@@ -8754,9 +8754,10 @@ so its point at `t` moves by (dx, dy), turning a straight spine into a curve (`p
`object.blend.setEasing {id?, easingType?, ramp?, colorShift?}` sets one blend's easing and color shift (the
first selected blend without `id`) and returns `{id, easingType, ramp, colorShift, changed}`; omitted values are kept.
`ramp` is 0 to 100 and `colorShift` -100 to 100. `easingType` and `ramp` need a blend whose steps follow a spine (a
replaced or edited spine, or `orientation: "path"`) and not made without one (`createSpine: "never"`), as the Blend
panel's Type and Ramp do. A value out of range, a hidden or locked blend and a target that is not a blend are errors,
`easingType` is `easeIn`, `easeOut`, `easeInOut` or `easeOutIn`, `ramp` is 0 to 100 and `colorShift` -100 to 100.
`easingType` and `ramp` need a blend whose steps follow a spine (a replaced or edited spine, or
`orientation: "path"`), as the Blend panel's Type and Ramp do. A blend made without a spine
(`createSpine: "never"`) takes them once Replace Spine has given it one. A value out of range, a hidden or locked blend and a target that is not a blend are errors,
and a call that changes nothing records no undo step (`changed: false`). With one blend selected that has a spine,
the Selection and Blend tools show the same values as widgets
16 px above and below the spine's halfway point (where the boxes of three or more other visible objects hold that