Is the 'page swiper' UI component supposed to work?

I'm trying to build a scene in myDesigner where I have static content in the bottom half of the screen and can swipe through 2 or 3 'sub-screens' in the top half. I thought that's what the page swiper component was for. I created the main scene page, created two overlays with different content, added a page swiper to the main scene and added the two overlays to it in the 'Page Overlays' area. But when I display the scene either in the simulated remote in myDesigner or the real smartremote the page swiper area remains blank. Am I doing something wrong?

I note that none of the provided samples use the swiper.

Andrew

I originally had designs on doing something similar for organizing device settings but have never been able to get the swiper to work. The best I was able to do was to use the scrolling section widget as a poor man's version of this, but it was clunky and I scrapped the idea.

I'll be interested to see what feedback you get on this.

Yeah I want the sub-pages to snap across, not smooth scroll stopping at any point (I tried the scrolling area too). If I can't do it I suppose it will have to be popup overlays.

Andrew

Nillaz, in your video, you had one screen where you were swiping left to pull in a screen "hidden" to the right (your lights, plugs, timers, etc. page), what control did you use there?

randyf wrote:

Nillaz, in your video, you had one screen where you were swiping left to pull in a screen "hidden" to the right (your lights, plugs, timers, etc. page), what control did you use there?

That's a point. Just here  it looks like you're using the page swipe.

Andrew

randyf wrote:

Nillaz, in your video, you had one screen where you were swiping left to pull in a screen "hidden" to the right (your lights, plugs, timers, etc. page), what control did you use there?
 

This would be super complicated to explain in depth, but the gist is that this is the one place where I did end up using the scrolling section widget locked to horizontal scrolling rather than vertical, in which the overlay that it is linked to has two more embedded overlays side by side locked to vertical scrolling. It's super kludgy to do it this way and I imagine that playing overlay-ception the way I am doing has a performance impact, but ultimately I was able to make it work out because there's only the "main activity" screen and the "settings" screen.

If you have more than one additional page it has a significant drawback in that there is no detent and like Andrew I would definitely want it to snap from page to page. Smooth scrolling the way the scroller works requires too much precision for this type of work on a 3 inch screen. It would be way easier to setup, maintain, and use in practice if you could just use the page swiper, drop in a few overlays, and flick between them.