# Swiping Cards in Perspective

**URL:** <https://forum.inductiveautomation.com/t/swiping-cards-in-perspective/21402>\
**Category:** Ignition Early Access\
**Created:** [December 13, 2018, 3:22pm UTC](https://forum.inductiveautomation.com/t/swiping-cards-in-perspective/21402 "2018-12-13T15:22:58Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [December 20, 2018, 9:44pm UTC](https://forum.inductiveautomation.com/t/swiping-cards-in-perspective/21402/2 "2018-12-20T21:44:53Z")

</div>

The important part (at least, re: swiping) is actually a carousel. I’ve attached an _extremely_ basic example with two different pages in a carousel - each is actually the same view, but with a different number of ‘cards’ visible. The ‘Card’ view is just a coordinate container; then the ‘Page’ is a flex container with a flex repeater within it. On the ‘Landing’ view, the carousel is set to ignore the default view height and width, then then also set to take the entire space available in _its_ container - a coordinate container set to ‘percent’ mode.

[Cards.proj](https://us1.discourse-cdn.com/inductiveautomation/original/2X/8/8c049592e3c1db1c8f8d668cfad8fc8c92ea53f3.proj) (4.0 KB)

---

_[View the full topic](https://forum.inductiveautomation.com/t/swiping-cards-in-perspective/21402)._
