we found a bug where the layer of a slide doesn´t resume to saved state when you revisit it. It works fine as long as you stay on the slide which contains the layer, but as soon as you go to the next slide and want to go back, it resets the layer.
I'm really sorry you ran into this bug, but I appreciate you bringing it to our attention! Now that we're aware of it, we can begin looking into a fix.
For anyone else who may run into this bug in the future, here's the scoop. We're finding that an object on a slide layer does not resume it's saved state after returning from previous or succeeding slides when base slide is set to "Automatically Decide".
Until we have a fix in place, you can work around this bug by setting the revisiting properties of the base slide to "Resume Saved State" instead of using "Automatically Decide".
Thanks again for helping us squash this bug, Susi! We always appreciate everything you offer here in the forums. 😊
actually I forgot to set the baselayer to reset to initial state in the demo I send you. We want everything to be resettet except this one slide.
I attached another file to my case with the original slide, it´s on the third "Resümee" layer/navigation point. I wrote second slide in the case notification but I think you can imagine which I meant. :D
Hopefully you can fix this, because we like those little interactions we build, but if the user has to do them over and over again when he wants to review the slides it could be a little annoying.
Thanks, Susi! I see that Angelo did some additional testing and sent an updated copy of your file as well. We'll keep an eye on your case as you continue working with Angelo, and we do have that one issue reported as a possible bug! We'll let you know once we have any more information on that too.
as it seems its working as it should, we just have to change the baselayer to "automatically decide" and reset or resume the layers to let them behave the way we want to. We normally reset every slide to the initial state and just wanted interactive layers to resume to the saved state when revisiting the slide.
In older versions (I think even SL2) it worked with the baselayer set to reset the state and layers to save their state so we thought it´s a bug, but we just didn´t understand the "audomatically decide" function. :) So now we got it figured out thanks to Angelo.
But funny my demo slide doesn´t work the way it should. Maybe there is still a little bug, but it depends on how you build the interactions on the layers.
Thanks again to the Articulate team for helping us as always fast and very nicely. ♥
Thanks, Susi. Thanks for updating your discussion title as well! I'm glad Angelo was able to help you, and if you need us to take a further look, please don't hesitate to let us know!
As there been an update to this fix? I'm in a similar situation where I need to lock down the seekbar so users can't skip ahead; this also means I need to create a trigger to disable the 'next' button when timeline starts, and create a another trigger for the 'next' button to normal when the timeline ends. When I advance to the next slide, and hit previous to revisit the slide, it does not save the initial state. The next button is disabled, and so is the seekbar. I'm stuck on that slide. Is this normal or is there a variable that can fix this? Please help!
Oh no! Sorry you've come across this issue on the latest update, Jason.
I see our team is still looking into this problem, but I'd like for our Support Engineers to test your .story file so we can explore some custom approaches in the meantime. If that works for you, please use this private upload link. We'll delete the file after we have a close look!
It looks like Ronaziel received your project file and is carefully testing it as I type this. Thanks for sending it in! You should hear back from her soon, and I'll follow the case along! 😊
12 Replies
Hey Susi,
I'm really sorry you ran into this bug, but I appreciate you bringing it to our attention! Now that we're aware of it, we can begin looking into a fix.
For anyone else who may run into this bug in the future, here's the scoop. We're finding that an object on a slide layer does not resume it's saved state after returning from previous or succeeding slides when base slide is set to "Automatically Decide".
Until we have a fix in place, you can work around this bug by setting the revisiting properties of the base slide to "Resume Saved State" instead of using "Automatically Decide".
Thanks again for helping us squash this bug, Susi! We always appreciate everything you offer here in the forums. 😊
Hi Alyssa,
actually I forgot to set the baselayer to reset to initial state in the demo I send you. We want everything to be resettet except this one slide.
I attached another file to my case with the original slide, it´s on the third "Resümee" layer/navigation point. I wrote second slide in the case notification but I think you can imagine which I meant. :D
Hopefully you can fix this, because we like those little interactions we build, but if the user has to do them over and over again when he wants to review the slides it could be a little annoying.
Thanks for your help and always fast answers. ♥
Susi
Thanks, Susi! I see that Angelo did some additional testing and sent an updated copy of your file as well. We'll keep an eye on your case as you continue working with Angelo, and we do have that one issue reported as a possible bug! We'll let you know once we have any more information on that too.
Hi Ashley,
as it seems its working as it should, we just have to change the baselayer to "automatically decide" and reset or resume the layers to let them behave the way we want to. We normally reset every slide to the initial state and just wanted interactive layers to resume to the saved state when revisiting the slide.
In older versions (I think even SL2) it worked with the baselayer set to reset the state and layers to save their state so we thought it´s a bug, but we just didn´t understand the "audomatically decide" function. :) So now we got it figured out thanks to Angelo.
But funny my demo slide doesn´t work the way it should. Maybe there is still a little bug, but it depends on how you build the interactions on the layers.
Thanks again to the Articulate team for helping us as always fast and very nicely. ♥
Susi
Thanks, Susi. Thanks for updating your discussion title as well! I'm glad Angelo was able to help you, and if you need us to take a further look, please don't hesitate to let us know!
Hello,
As there been an update to this fix? I'm in a similar situation where I need to lock down the seekbar so users can't skip ahead; this also means I need to create a trigger to disable the 'next' button when timeline starts, and create a another trigger for the 'next' button to normal when the timeline ends. When I advance to the next slide, and hit previous to revisit the slide, it does not save the initial state. The next button is disabled, and so is the seekbar. I'm stuck on that slide. Is this normal or is there a variable that can fix this? Please help!
Hi Ruthya,
Looks like I just responded to a similar post here.
I just ran into this issue in version Build 3.25.18009.0.
Layer (On the Master slide) was set to Resume Saved State, and Base Layer is set to Reset to Initial State. The Layer is not resuming saved state.
Oh no! Sorry you've come across this issue on the latest update, Jason.
I see our team is still looking into this problem, but I'd like for our Support Engineers to test your .story file so we can explore some custom approaches in the meantime. If that works for you, please use this private upload link. We'll delete the file after we have a close look!
Katie,
I did upload the story file when I submitted the support case. Just let me know if I need to re-upload. Thanks!
Good morning, Jason!
It looks like Ronaziel received your project file and is carefully testing it as I type this. Thanks for sending it in! You should hear back from her soon, and I'll follow the case along! 😊
Thanks Katie!
This discussion is closed. You can start a new discussion or contact Articulate Support.