States not saving in Master Slide

Aug 04, 2015

I have a .story that uses checkboxes on a master slide that use triggers that will change the state of the checkbox to being "checked" when a variable has been activated in the .story by the learner.

It works most times but I find when I save the triggers in the master slide close it and open it again the custom state of "checked" which I have created instead of "selected" always seems to get removed and defaults to the default "selected" state which I don't want. I have to end up creating the "checked" state all over again pretty much every time I open this file.

Is there anything I have to do? If you could please let me know that would be great thanks. 

6 Replies
Christie Pollick

Hi, Diane -- Sorry to hear about the issues you are experiencing, but there are a few general troubleshooting steps we can run through to rule out the causes of some common issues. Please make sure you are working locally as described here, and you may want to try importing the file into a new file. If you are still having issues, you might want to try to repair Storyline.

If issues persist, you are welcome to share your .story file here and we can do some testing on our end.  Please use the ADD ATTACHMENT button in the bottom left corner of the reply box in the thread, and you can browse for the file from there. Please also note that if you reply via email, your attachment will not appear here in the thread. Thanks! :)

Diane Fung

I am working locally and I'm not sure  how much importing slides would help. I've attached the .story file and a screenshot hopefully shows where the problem is happening. As soon as I close the .story file and reopen it I have to reset the states of the checkboxes back to the "checked" state that I created. 

 

Christie Pollick

Hi, Diane -- Thank you for your patience, and after reviewing your file, I am seeing the same behavior as you. I tried ungrouping the item to see if that would help, and also tried reimporting the file into a new one, and neither did the trick. I will go ahead and create a support case for you (00621945), and you will be hearing from one of our Support Engineers shortly. I intend to follow along with their progress and will update the thread if a resolution is determined for others who may come across this thread if they are having similar issues. 

Diane Fung

Thanks for looking so deeply into this. I don't mind resetting the states because I do need the file to work and it seems fine I just have to reset it every single time I reopen it but it still seems like a problem in the software.

Additionally I've noticed that the story.html version vs. the story_html.html version differ in their stability.

When I've published and tested in the html5 version when the learner finds one of the "scavenger hunt" items I have a layer that appears to give the leaner some feedback. After it is "closed" using the "x" button, the "tabs" that I created using layers don't seem to work anymore. This ONLY happens in the html5 version but the regular flash based story.html works perfectly.

I'm going to use the flash story.html version for now but in the future will there be updates/patches that will help Storyline publish/render the triggers/layers better? I know HTML5 is fairly new and that the Articulate Storyline team is probably working on it but is this something that is being looked into? I'm just curious as I'd like to ensure that we can use our material for tablet's and mobile going into the future. Thanks again for all your effort into this.

regards,

Diane 

Christie Pollick

Hi, Diane -- Thanks for the feedback, and I see that Robert from our Support team has replied via email after doing some testing on your file. With respects to your question as to whether or not there will be updates/patches that help Storyline publish/render the triggers/layers better, unfortunately, we do not announce product roadmaps or release dates for new products/features or updates. You are welcome to share your thoughts on features you'd like to see by submitting a feature request here as those go directly to our product development team! :)

This discussion is closed. You can start a new discussion or contact Articulate Support.