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

I decided to try this "swipe" feature, and ran into some discrepancies, and wanted to see if others are seeing the same thing. I made the swipe area the full screen for my overlays. And like mentioned previously, I also had to do an app clear cache on the smartremote before I started to see anything.

On my swipe area, half way down are two "LT/GT" (< >) type arrows for the user to use to swap pages. I did not see those arrows on the previous screen shots that are in this thread. If there is going to be a future provision to hide the bottom dots, then perhaps the option could be extended to those arrows as well.

The swiping itself is inconsistent. Swiping in the middle of the screen does nothing, I had to swipe along the top edge of the screen to get it to swap. The bottom of the screen swipe works, but only sometimes.

There does not seem to be a way to programmatically force a swipe or to switch to a specific overlay. The Hide and Show client commands appear to be disabled. Is there a way I am not aware of?

I have the page forward / page back arrows on mine.

The swipe gesture took me a little bit to get used to. Swiping from the edges like I would typically do on my phone was wildly inconsistent. Swiping from the middle of the screen works much better for me, though I had to sort of mentally train myself to do so.

The backwards and forwards arrows are extremely tall (and very annoying). Maybe you're starting your swipe on an arrow which I suspect wouldn't work.

Andrew

I've added the option to hide the paging buttons. You'll pick up the change the next time you do an "Update Project" in the Designer. The pager will now default to hidden paging buttons. When you edit the pager you'll see a checkbox to enable the paging buttons.

There are also client commands to build your own paging buttons. It requires giving the pager a friendly unique name via the Rename button.
If the friendly name is swiper12  then the following Client commands are available.
PageSwiper|<<friendlyname>>~prev       go to previous page
PageSwiper|<<friendlyname>>~next       go to next page
PageSwiper|<<friendlyname>>~1..N       go to page N

There might still be some issues in the pager. I'll have more time to work on it later in the week.

davep wrote:

I've added the option to hide the paging buttons. You'll pick up the change the next time you do an "Update Project" in the Designer. The pager will now default to hidden paging buttons. When you edit the pager you'll see a checkbox to enable the paging buttons.

There are also client commands to build your own paging buttons. It requires giving the pager a friendly unique name via the Rename button.
If the friendly name is swiper12  then the following Client commands are available.
PageSwiper|<<friendlyname>>~prev       go to previous page
PageSwiper|<<friendlyname>>~next       go to next page
PageSwiper|<<friendlyname>>~1..N       go to page N

There might still be some issues in the pager. I'll have more time to work on it later in the week.

Any chance you could do the same for the paging next and previous arrows - a checkbox to show or hide them? Thanks.

Andrew

Okay, I surrender. I have been trying to get the PageSwiper command to work, but no success. The cause may be some newbie mistake I am making though.

I have updated the project with the update project button in the designer. Is there some other button or thing I am supposed to do as well to update? On the screen, Swiping and using the page next/prior default buttons seem to be working as expected, it is just the PageSwiper command I can't seem to make work.

I went in and opened the "fxapp.js” Javascript file that is in my project’s subdirectory, to see if I can see anything. The “PageSwiper” code is present, but I suspect there is a problem in that the “next” case may be calling the wrong method (it is calling the method “prev” in my source, just like the “prev” case also does). I made sure to test my code using “prev” or the explicit page number, just in case.

Here is my client command:

PageSwiper|swiperhouse~prev

Where “swiperhouse” is my unique “friendly” name for the swiper component.

I also notice that the “Show Page Icons” check box does not remain checked after the acene save.

I remember that Davep is still working in this area, so maybe these problems are already fixed, just not distributed.