alt text dont workie

jill 2021-04-23 18:49:16 +00:00
parent 52ab5286d7
commit 3966e9a575
1 changed files with 9 additions and 1 deletions

@ -96,15 +96,23 @@ Think of it this way. Each ease function in Mirinda is an `inOut` function, mean
![inOutCirc with the align set to 0.5. Purple is the ease, and red is the alignment point.](https://e-six-two.one/i/nq3z.png)
*inOutCirc with the align set to 0.5. Purple is the ease, and red is the alignment point.*
Functions like `wiggle` or `onoff` use the whole thing, where `kick` or `sharponoff` trim off one end to create a sharper ease. This way, if you were to change the ease to an out or in ease, everything would break pretty badly unless you use `:align()` on it to change the alignment to the start or end:
![outCirc with the align set to 0](https://e-six-two.one/i/wwxi.png)
*outCirc with the align set to 0*
This system works really well with eases that aren't aligned to the middle or start/end. For example, if you want an ease to have a long in part but a quick out part, you can use the `:mixease(ease1, ease2, a)` standard function to mix two eases and do the alignment stuff automatically. For example, here's approximately what `:mixease(inCirc, outCirc, 0.75)` would look like:
![mixease(inCirc, outCirc, 0.75)](https://e-six-two.one/i/6dpz.png)
*mixease(inCirc, outCirc, 0.75)*
You'll notice the end is significantly sharper than the start, and the alignment point is still aligned with the middle. You can also mix different eases this way, and not specifically the same type of ease.
This is what `mixease(linear, outCirc, 0.75)` would look like:
![mixease(linear, outCirc, 0.75)](https://e-six-two.one/i/dxur.png)
![mixease(linear, outCirc, 0.75)](https://e-six-two.one/i/dxur.png)
*mixease(linear, outCirc, 0.75)*