Forum Discussion
On revisit, having the layer resume to saved state
I'm having some trouble with the layers returning to the saved state. I have things occur on a layer (like an item sliding in or a motion path).
Slide 1. 1 layers. Both the layer and the slide are set to resume saved state. On revisit, the slide goes to layer 1 but the layer hasn't completed yet, so the animation replays. How do I change the setting so clicking the back button to revisit layer 1 will result in the learner seeing the END of the layer 1 timeline versus starting at the beginning of layer 1 timeline? I don't want the slide animation to re-occur when the user clicks the back button.
Besides a bazillion triggers and variables, how do I make this happen? (I could maybe do a Slide 1=true when the user clicks the next button. And, if slide 1 = true then have timeline start at XX (end of timeline or something. But this has to be easier than that right?)
I'm having a similar issue with Slide 2. User goes to slide 3. Clicks back. Last layer of slide 2 appears but the user still has to click the next arrow to get the animation to trigger and check the form. I want the form to be checked already on re-visit.
Review Tool Demo: https://360.articulate.com/review/content/c63295bb-9308-41c1-aeec-0df4e478ce32/review
12 Replies
- RonPricePartner
I would recommend submitting the case as this is not the expected behavior.
- ElisabethHCommunity Member
Thank you. I just did. I was so sure I wasn't doing anything wrong!
- SusanTam-1c3fb5Community Member
I am experiencing the same bug. I say bug because a month ago everything was working fine. Today, while doing updates, my layers are replaying each time I go back to the slide.
- ElisabethHCommunity Member
I did submit a case. It's happening on other projects now for me as well.
- ElisabethHCommunity Member
It looks like this is a known bug (not that Articulate told me that when I opened a case). Here is more info and a suggestion to downgrade to an earlier version of SL. https://community.articulate.com/discussions/articulate-storyline/layers-set-to-resume-saved-state-are-not-working-properly
- SusanTam-1c3fb5Community Member
Thank you for sharing! I feel your pain. I have already lost several hours to this. I also submitted a case.
Hi Susan,
Thanks for reaching out and I'm sorry to hear you're experiencing this issue. I see Woojin has reached out to you in your case so we'll continue the communication there!
Hi E-Learning Person,
I see you've connected with my teammate, Ian, about this! We'll be sure to update you with any news!
- AnneDeFeliceCommunity Member
I am having a similar issue with a Storyline block within Rise.
Edit: I posted the issue at the thread you referred to above as it seems to be more current. https://community.articulate.com/discussions/discuss/layers-set-to-resume-saved-state-are-not-working-properly/887499
Hi Anne,
Thanks for reposting your question to the more current discussion! I see that my colleague Kelly responded. We can continue the discussion in that post to keep the information in one place.
- theodorogomezjrCommunity Member
This also happens when trying to use a variable to update button states on a slide master.
When a button (also tried as an image) with several states is placed on the slide master it only works as intended when the variable change happens on the slide, it works as expected.
The variable reference value works globally, no problem there.
But when you apply that master slide (with button and variable placeholder) to another slide, where the change is not initiated, it handles the variable reference just fine, but the button reverts to its initial state.
Even used a different mater slide, nothing. Placed the button, (or image), with states and variable update triggers on the actual slide, no dice. And slide triggers do not allow you to select the button from the master slide to update so no luck there.
Seems like another trigger event might be in order, something like:
Change state of button when "slide is revisited" or "slide load".
- theodorogomezjrCommunity Member
Solved this. i place the trigger on the master slide, tho i thought i had already tried that :)