1

As you may know, with the (Auto)Rotator you can create slideshows. Unfortunately, the UX when using touch events or gestures isn't what you'd expect. For example, if you wanted to use a swipe gesture to skip to the next slide, the slide wouldn't actually stick to your finger/pointer because the Rotator only provides simple transitions, which are invoked by itself through basic commands like "next".

Is it possible to adapt the (Auto)Rotator to work like a typical gesture-based slideshow, and - if so - how? Or would it be less of a hassle to just program it myself?

DanMan
  • 10,431
  • 3
  • 36
  • 57
  • This comment regards your comment [here](http://stackoverflow.com/a/4026505/1525840). You were clear that there are specific rules and the ambiguity is negligible when designing REST. Would you care to share a link pointing to a resource (pun intended) that discuss it? I'm asking, because in my experience, there's often need to be creative and flexible and it would be good to know if the flexibility is perhaps voiding the convention. – Konrad Viltersten Nov 22 '16 at 09:12
  • @KonradViltersten Not off the top of my head, no. Sorry. – DanMan Nov 22 '16 at 17:42

0 Answers0