Saved State and the Rewind/Playback button logic
May 20, 2014
I have been pretty vocal about this issue in an old post and figured that I will make a new post to maybe get some traction from other Storyline users.
Can someone please tell me the logic of why when slides are marked 'Resume in the Saved State' that the playback button does not work? Who at Articulate thought this was a good idea and how did this get the okay to get developed. Essentially, what you have when the slides are set up like this is a broken button for the learner to become frustrated with all of the time.
I have read the documentation on how the playback button works and for you to tell me that that it works dependently with the state of the slide is ridiculous. Why can't the learner go back to a slide in the saved state and pick up where they left off and also replay the slide if they missed information? These need and should have always been independent. The fact that you have allowed a broken button to remain on screen and continue to tell the users of your software that this is how this was meant to function is unbelievable and a slap in the face.
I have submitted an enhancement request and will continue to be a thorn in your side until this is fixed because this should have been done a long time ago. I don't know when the next update will be, apparently Articulate doesn't have a road map of issues they would like to fix, but hopefully it will be soon. If not, then the people who run this software company are clueless. I would like other users to get on board with this and maybe this will be addressed in the near future. Fingers crossed.
6 Replies
Hi Brian,
I wanted to let you know I've shared this thread with our QA team for additional review, but as you mentioned this is considered to not be a bug but by design as detailed in this article. To change that behavior, submitting a feature request is the best way to share your thoughts with our product development team, and for anyone else who comes across this thread and agrees can also submit a request here.
Our team is regularly working on updates to all of the Articulate products, but we don't release a road map or schedule of when updates/new versions would be released. I'd suggest that following along with our Word of Mouth Blog, and following Articulate on Twitter and Facebook as well.
Hello Ashley,
Thank you for forwarding this to your QA team. I am actually a pretty nice guy but also expect that the instruction I provide to our partner base be the best that it can be. I look forward to hearing something from the QA team to that this issue will be fixed or some very sound reasoning as to why it will remain the way it currently is. Hopefully it is not the latter because I believe this is pretty cut and dry. Thanks again.
Hi Brian,
I'm happy to pass along the message. I don't have a time frame for when I may hear back from our QA team, so I'd suggest to ensure you're subscribed to this thread as well as I'll provide any updates here directly. In the meantime, if there is anything else I can do to assist please let me know.
Posting to this thread because I'm gobsmacked that this was posted by Brian Seaman over 5 years (!!) ago.
The Rewind button should function as a Rewind button. Simple as that.
Yes, I put in a Feature Request.
totally agree, I'm having to troubleshoot a similar issue now - which is why I'm researching the forum for answers. Good call out.
Thanks for submitting a feature request, Greg.
This is one that we're tracking and I've tagged this conversation and your feature request so that we can share any updates with you here.
I wanted to share some information about how we manage these feature requests as that may be helpful.
This discussion is closed. You can start a new discussion or contact Articulate Support.