Variable issues
Sep 10, 2013
Hi,
I have a course that uses variables to stop learners accessing the assessment content until hey have finished all modules by clicking the continue button at the end of each module which has said variable attached.
This all works fine. However on the module selection slide, once the learner clicks the button the button has a trigger to change the state to visited, in this case a large green tick appears over the button.
If the learner were to navigate back to this screen mid-module, they would see the green tick over the button and may believe that they have completed.
Therefore I tried altering the trigger to take into account the variable at the end of each module.
So therefore it would only turn green once this had actually been completed.
I don't know why. It just refuses to work. In the trigger viewing pain, the triggers are refusing in the cases of button 2 & 3 to even recognise the variable. Button 4 does... but does it's own thing.
Can anyone see where I have gone wrong?
Many thanks.
(am attempting to upload a test .story file for you)
8 Replies
.story file
Good Morning, Tim.
I'm having some trouble reproducing the problematic behavior, as your .story project file seems to be behaving as you've described you'd like it to work. Please take a look at the following Screenr:
Is there something I have misunderstood? What is the best way to reproduce the problematic behavior? Thanks!
Hi Justin,
Many thanks for your time.
The problem seemed to be if I did not click the continue button and navigated via the menu back to the module selection screen - the green tick still appeared
Would you try that for me to see if it still happens?
Thank you again
Visited is a built in state you should be using a custom state for this, you have the slide set to resume saved state as visited just means clicked it will change as soon as you press it. Otherwise you have it set up correctly.
See the file I have attached which has a good annotated example.
Thank you Phil and Justin, I don't have time to check it tonight, but will let you know on Friday... does make sense though.
Glad Phil and Justin were able to help you out Tim, thanks for sharing
Thank you all, it's working all fine, I would never have figured that one out on my own.. I never considered that the 'visited' state would work differently to what I wanted.
It threw up one or two more issues when I resolved it to do with other triggers that relied on 'resume saved state' etc, but easily put right by including the variables in them.
Thanks for the update Tim! Always learning
This discussion is closed. You can start a new discussion or contact Articulate Support.