# \[Processing\] Unfolding columns

**URL:** <https://discourse.processing.org/t/processing-unfolding-columns/610>\
**Category:** Gallery\
**Created:** [June 1, 2018, 10:47pm UTC](https://discourse.processing.org/t/processing-unfolding-columns/610 "2018-06-01T22:47:24Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![jeremydouglass](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/jeremydouglass/32/20_2.png) [@jeremydouglass](https://discourse.processing.org/u/jeremydouglass)\
**Post date:** [June 4, 2018, 8:36pm UTC](https://discourse.processing.org/t/processing-unfolding-columns/610/5 "2018-06-04T20:36:21Z")

</div>

> [@WakeMeAtThree](#):
>
> I’m using shear, rather than rotate, to show the depth of the unflattened shape. That way, the top side of the shapes maintain the 90 degree angles, and when combined with `ortho()` mode, keeps lines parallel in an oblique projection.

That is a really useful tip. Thanks!

Beautiful work (is my continued reaction)…

Right now is each point your animated primitives doing a linear point-to-point transform, or do any of them have multi-step paths? I ask because I’ve been toying for a while with submitting list-based interpolations (lerp → lerps, lerpColor → lerpColors) as a Processing feature proposal or as a lightweight library.

- [https://forum.processing.org/two/discussion/25310/list-based-interpolations/p1](https://forum.processing.org/two/discussion/25310/list-based-interpolations/p1)

Your animations seems like a perfect example of how a lerps primitive might be useful for the processing audience – e.g. rather animating across two frames PVector[12][2] it could be PVector[12][3] and the inverted L would grow up first to the angle joint, then over.

---

_[View the full topic](https://discourse.processing.org/t/processing-unfolding-columns/610)._