Issues with logic of review questions
Sep 18, 2014
Hi,
I am trying to build a test with the ability to review answers but as a pop up window rather than going back through questions. The logic I am using I thought was sound but it doesn't seem to be working - can anyone help?
Basically there are 10 questions slides and 1 results slide. There are 10 variables (1 per slide) that are set to false. If the user clicks a next button a trigger is activated to turn the variable to true if the right answer is selected (is this the correct way to do this). This continues per slide and finally when the results slide starts a serious of ticks and crosses have triggers (40 in all) for both hiding and showing. They state that for example, when the timeline starts if variable ResultQ1 is true show tick, if ResultQ1 is true hide cross, if ResultQ1 is false show cross, if ResultQ1 is false hide tick.
Unfortunately all I get is a bunch of crosses and no ticks no matter what I do, this is telling me that the variable remains false. So I'm guessing that the logic on the individual slides is not sound; is 'selected' the correct way to do it? I figure visited but then I could visit all of them and probably turn the variable true even if I eventually end up submitting the wrong answer....?
Any help would be greatly appreciated!
Thanks in advance.
-Aly
6 Replies
I should also add in that all the questions are multiple choice radio buttoned questions... thanks.
Hi Christoph,
I can't open your file, says it may have been made in a newer version of articulate...!
What did you use to tell articulate the user had clicked on the right or wrong answer?
I can see these states -
Normal
Hover
Down
Disabled
Selected
Hidden
Visited
I would have thought selected was the one to use?
Hi,
I tried what you suggested.. makes more sense - Unfortunately it doesn't work! So I don't know if the fact I have this logic on a separate layer would make a difference?
I've tried placing the logic elsewhere. In theory I could call up the code when the user clicks on the button that reveals the layer. I may try that next. So far I tried putting the command to hide all crosses and ticks on the lowest layer and commands to reveal depending on the state of the variable on the review answers layer. This basically made all ticks and crosses invisible!
What is your email address and I'll send it over.
So I found the issue. On the individual question slides the call to change the variable had to be the first function to be called before anything else, which in my case was before the submit interaction function and obviously before the change slide function. Once I had changed this all slides worked as expected and results changed as expected.
Moral of the story is to give priority to the functions that are being difficult - making them the opening act will convince them to function better.
Thanks Aly for the update here - and trigger order is very important, and they'll be executed as described here.
This discussion is closed. You can start a new discussion or contact Articulate Support.