Forum Discussion

ArjanWeise1's avatar
ArjanWeise1
Community Member
28 days ago

Layer swipe and button conflict

Your support please.

I have created a Project that allows swiping between layers. For users on devices that don't allow swiping I created buttons. But now if you use the buttons on a touch screen it randomly proceeds multiple layers (so it does not advance one but two). Or when ticking back it goes back one and advances one. 

Swipe test


To enable swiping, I:

created a variable to activate the layer that should be visible

created the layers

added a swipe trigger on the base layer: 

On the base layer:

  • Swipe Left → Next Layer

o   Action: Adjust variable

o   Variable: Layer

o   Operation: Add 1

o   When: User swipes left

o   Condition: currentLayer < 5.

  • Swipe Right → Previous Layer (optional)

o   Action: Adjust variable

o   Variable: Layer

o   Operation: Subtract 1

o   When: User swipes right

o   Condition: currentLayer > 1.

Added Triggers to Show Layers

On the base layer, create triggers that fire when Layer changes:

  • **Show Layer1 when **Layer == 1
  • **Show Layer2 when **Layer == 2
  • … repeat for all layers.

Trigger settings:

  • Action: Show layer
  • When: Variable changes
  • Variable: Layer
  • Condition: Layer == X.

Did the same for the navigation buttons (same logic)

Added a  Backup Function (Sync Variable on Timeline Start)

On each layer:

  • Add a trigger:

o   Action: Adjust variable

o   Variable: currentLayer

o   Value: X (the layer number)

o   When: Timeline starts on this layer.

This ensures that if a learner jumps to a layer by another method (e.g., menu), the variable stays in sync.

4 Replies

  • Hello ArjanWeise1​
    Thanks for reaching out!  I tested your Review link on my end, and was able to successfully swipe from slide to slide without that jumping behavior you described. I'd like to learn more!

    • What device are your learners viewing this course on? I'm curious if this issue is only occurring in a mobile phone or perhaps on a tablet. 
    • Are your learners viewing this in Review 360 or another publishing option?  It would also be helpful to know the browser(s) being used if in a web environment.

     

    We'd be happy to take a closer look at your .story file and a screen recording of this behavior to continue troubleshooting. You can share these materials in this thread or privately in a support case

    Looking forward to hearing from you! 

    • ArjanWeise1's avatar
      ArjanWeise1
      Community Member

      Hi Luciana, thank you for your reply. 

       

      I have been testing this on My Samsung A52 as this phone is widely used in our audience. 

      I find the issue in both Review360 and when I publish to our LXP (Docebo). Although it seems to work a bit better when published it is far from ok.

      I forgot to save the .story file so I had to build the test case over. So it might look a bit different from the one I first shared. The issue is the same.

      In the video you can see the swipe function works well, but when I start using the buttons it starts to skip layers.

      I created a new review link for this project

      https://360.eu.articulate.com/review/content/955c26f3-79da-4f37-a935-c1e1140b5bb1/review

      Hope you can help!

      • LucianaPiazza's avatar
        LucianaPiazza
        Staff

        Hello ArjanWeise1​

        Thanks so much for sharing a screen recording and sample file in this thread! 

        Since this behavior appears to be isolated to your setup, I've opened a support case on your behalf so our talented Support Engineers can continue troubleshooting the issue you're experiencing with your Samsung A52. They will be in touch shortly via email. You're in excellent hands! 

        We'll continue the conversation in our case, so everything is in one spot!

  • I would suspect this is a trigger order/timing issue.

    You show the layer and then subtract one or add one, but you also set the value on timeline start of the layer.

    The layer is loading and then the trigger fires to add one which adds to the layer you have just shown. Because the nav triggers are on the baselayer they will fire in order.

    Solution? I am not sure you could change the trigger order or just have the swipe add and subtract andthen show the layer when the variable changes and use the same function for the other method of showing the layer