Forum Discussion

KatMagnuson1's avatar
KatMagnuson1
Community Member
9 years ago

"Resume Saved State" - no longer works if Next button disabled when timeline begins?

From the tutorial: "Resume saved state: Use this option if you want the slide to always remember its previous state. In other words, this option lets learners pick up where they left off when they l...
storyline 360
StianLarsen's avatar
StianLarsen
Community Member
6 years ago

Did some more searching. The "timeline starts" trigger is supposed to always fire? It cant have been like that since the beginning, as I've uses these functions before. 

I even tried using "when timeline reaches 0.25 sec" and "0.5 sec", and "2.0 sec", but its still returning to disabled instantly upon going back one slide. Are there known bugs to this at the moment? Because I cant seem to find a way to keep the next-button disabled untill the user have completed the requested actions. Going back to this slides renders the user unable to ever move forward again.

  • WendyFarmer's avatar
    WendyFarmer
    Super Hero
    6 years ago

    Hi Stan

    I remembered seeing this post recently - not sure if it helps you 

     

    • StianLarsen's avatar
      StianLarsen
      Community Member
      6 years ago

      Thanks. I do not agree that this is "by design", as there is no reason why one cannot do a trigger the first time a slide loads, but not every time it loads even when the state is resumed.

      I even tried using "when timeline reaches 2 sec", but it will still immediately trigger and set it as disabled when you revisit the slide. So there must be some sort of a bug there either way. If by design, it should still either take 2 sec to turn disabled upon revisiting a saved-state slide, or it should not trigger at all, as the timeline should not progress.

      I have a deadline today, and it looks like I have to go over all my pages in all my current projects and add an invisible object with a "completed" state on it. Change the state of this object to complete, and do a condition on the next-button upon revisiting. Set state of Next-button to disabled when timeline starts if <State of Shape X> is not COMPLETED. 

      Does not look like an intended way of doing this, as its just not intuitive. Why do I need extra triggers and invisible object on the slide, with states, to prevent the button from being disabled upon revisiting a saved slide. Seems like a bug got in there somewhere, and they dont want to correct this. A lot of people must use this for of navigation.