HTML5 Button States Problem

Jun 11, 2013

Hi there,

Having a few problems with getting buttons to stay hidden on HTML5 output and would appreciate some help. 

Here's what I want to do. 

Create a Pick One Freeform activity with x number of buttons. Set to x attempts.

When you click on an incorrect button - I have the following triggers setup:

1. Set Clicked Button 1 to Hidden

2. Submit Interaction

In Flash version this works perfectly - The Try Again - Dialogue Box Appears - I click on ok and Button 1 is gone

In HTML5 version -when I click "ok" on the Try Again dialogue Box - Button 1 does not disappear. 

I can no way to make the button stay hiden on Freeform quizzes with HTML 5 output.

Can this be done? Would really appreciate some help.

Thanks in advance

5 Replies
Christine Hendrickson

Welcome to E-Learning Heroes, Andrew!

First, can you tell me what version of Storyline you're using, please? To find this information, click on "Help" and "About Articulate Storyline".

If you're not running version 3 (1305.2012), please download and install the update using the link below:

Articulate - Storyline Update 3

Once you've finished installing the update, please republish and test your course's HTML5 output. If the problem continues after installing the update, or if you already have Update 3 installed, please let me know.

Thanks very much!

Christine

ANDREW GARVEY

Hi Christine,

Thanks for the welcome. I'm running Update 3. I've created a sample story to show the problem. When I publish and run the Flash version (story.html) the button state works and stays hidden after clicking.

If I run the HTML5 version (story_html5.html) the button state seems to reset and won't stay hidden. 

Any suggestions on how to proceed would be most welcome.

Thanks

Christine Hendrickson

Hi Andrew,

I'm not quite sure why that's not working in HTML5. I tried it out and I can actually see the button change to "Hidden" when the "Try Again" prompt is open, but as soon as you return to the question it's back on the slide. 

Now, I did manage to find a little bit of a workaround for you, just in case you want to try it out. 

If you place the state change trigger on the "Try Again" button, it will actually hide the wrong answer when the user clicks this button. So, it is visible when the "Try Again" layer is open, but should be gone when the user returns to the slide:

Testing for Andrew

Would that work for you?

ANDREW GARVEY

Hi Christine,

Thanks for the reply. Yes, I discovered that workaround while trying to find a solution. It would work but is far from ideal to be honest. See attached image for the actual content - here we have 9 options - which explains why we're using the freeform quiz - as it simply wouldn't work from a design standpoint with a standard multiple choice quiz.

For the workaround to be implemented for the actual content (9 buttons) and please correct If I'm wrong. I need to do the following:

Assign a separate variable for each button

This is incremented by 1 on click (The answer they choose)

On "Try Again" layer - I need to set each each button to hidden if the variable value is 1 - so only clicked buttons are set to hidden

I see no other way to achieve the desired effect on HTML5 output.

If this is indeed the only workaround for HTML5 it's a lot of extra work to achieve the same solution which works perfectly with the Flash output. 

1 tigger and no variables (FLASH)  vs 9 triggers and 9 variables (HTML5)

If there's a better solution - please advise. 

Thanks very much.

Christine Hendrickson

Hi Andrew,

HTML5 is.. a little more finicky than Flash, in my opinion. While I realize additional work isn't appealing, if you must publish for HTML5, that may end up being the case. I am doing some testing on this specific issue, though and as soon as I have more I will pass this information on to our QA team for some additional investigation. This certainly is something I think is worth looking into, and I do agree that this isn't something you should have to modify to this extent.

The variables may be the way to go for this, for the time being. If you'd like, you're welcome to share the original project file with our support team. If we can take a look at the issue a little closer, hopefully we can get some details that will help fix this issue or maybe we can find an alternative solution for you that won't be so time consuming.

You'll be able to attach the .STORY file on the second page of the following form:

Articulate Support - Submit a Support Case

Please be sure to include a description of your issue. Please also include the URL for this thread in the form. Also, please share the case number with me. You're welcome to do so here, or in a private message. This way I can follow the progress of the case and update this thread.

Thanks very much Andrew,

Christine

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