feedback states on Ipad
Dec 12, 2012
hello.
I have a problem in a quiz on the Ipad.
I tryied something to display the good answer in green in the feedback and change color of the user's answer in red if it s wrong.
- So, first I created a multiple choice activity and add a correct state(green) and a incorrect state(red) to each propositions.
- then i created a variable which correspond to the number of the proposition selected by user. ex : If user clics on the second proposition then the variable will set to value=2. (etc)
- In the correct feedback layer, i create a trigger which change the state of the propostition which is the correct one to its green correct state. so in that case, the proposition selected by user should turn into green.
- in the incorrect feedback layer, i create the same trigger for displaying the good answer, and one other trigger to each other propositions which change state to their red incorrect states. for those triggers i add the condition
" if variable== Equal to "n" " which "n" is the number of the proposition.
so, for example : if the good answer is the first one and the user selects the 3rd, on the feedback, the 1st proposition will turn into green to show the good answer, and the 3rd (selected one) will turn into red. The others propositions won't change.
I thought it was a good way for displaying corrections, i tryed it on my computer and it works very fine !!!
but then i tryed it on an Ipad and ... ouch.
When i arrive on the quiz slide, the good proposition is already turned into its green correct state. And it is the same for each quiz slide, the good answer is displayed since the opening of the slide.
I attache the course that you could suggest me what to do to make it work on Ipad.
Thanks
ps : Sorry if i don't speak english very well, i just hope my explanation is understandable
4 Replies
Hi Anthony. Welcome to E-Learning Heroes!
I took a look at your files, and I have to say it looks great! I published the file, temporarily, so I could test it on my iPad. It's working perfectly for me.
Are you viewing the content in Safari, by any chance? If so, try publishing for the Articulate Mobile Player. If you don't have this installed on your iPad you can get it here.
If you'd like to test the version I published and tested on iPad, go here.
Let me know how it turns out!
Thanks,
Christine
I was viewing content in safari, so i tryed with Articulate Mobile Player and as you said, it works.
In conclusion, it works, but not on the html5 version...
But, what if the user decides not to install the app ?
what if he use an android tablet ?
Is there a way to fix that problem for html5 or need i to just try another way for displaying the solutions?
Good morning Anthony,
Good, I'm glad to hear it's working properly through the app. As for viewing through Safari, it may be due to limitations of the browser. If you'd like to see the comparison chart for Flash, HTML5 and the Articulate Mobile Player, please take a look at this article. Storyline's content works best from the AMP app on iPads, both Safari and HTML5 are known to have a few issues, due to the limitations. One thing you can check is the private browsing settings in Safari, but I'm not entirely sure it will change the appearance of the colors you've added.
Here's more information on Safari's Private Browsing:
You may find that Storyline's HTML5 output doesn't load as expected in Safari if the Private Browsing feature is enabled.
This is a known issue. To correct it, turn off Private Browsing while you're viewing your Storyline content. Here's how:
http://www.articulate.com/support/kb_article.php?product=st1&id=s22qzxqc5fo9
Now, in regards to your other question, it works a little differently for phones/androids. There's a lot of information on this topic in this tutorial. I think you might find the content and links in that tutorial helpful, but if you have any other questions let me know.
Thanks Anthony!
Have a great day,
Christine
Ok, I will try to find another way which could works both on flash and html5.
Thank you very much for your help.
This discussion is closed. You can start a new discussion or contact Articulate Support.