I have developed a jeopardy-style gameboard. When I developed it a month ago, it was working as expected. The board has 15 clickable buttons to take you to different questions. I have a variable that keeps track of the buttons you click that are still in the Normal state. This is important because learners need to go through every question for compliance reasons. When the tally reaches a certain #, a bonus question is revealed.
Since the latest update, the Tally variable is not being adjusted if I have the Normal state condition on it. I created a test file and have the same experience. I would appreciate any help/thoughts on this one.
It works in the attached file. All I did was change the conditions. Instead of checking whether the button state equals Normal, it now checks that it doesn't equal Visited.
FYI: "Normal" underlies all the states, so it's better to avoid conditions that refer to that state. Because sometimes it works, but not always...
BTW, the 1st button has a Selected state. That should be deleted. It's not needed, since the user leaves the slide before seeing that state. And, because the buttons aren't in a button set, the button stays in that state, even when other buttons are selected.
Finally, hurray for you preparing a test .story file! I appreciate getting a simple file for troubleshooting. 😄
You're welcome. I also played around with the triggers in the real file and found out that by deleting the built-in Visited state, it also works.
As far as the test file, the real one has probably 100+ triggers and variables and about 20 slides - it is a challenge for me to unpack, much less someone looking at it for the first time.
2 Replies
It works in the attached file. All I did was change the conditions. Instead of checking whether the button state equals Normal, it now checks that it doesn't equal Visited.
BTW, the 1st button has a Selected state. That should be deleted. It's not needed, since the user leaves the slide before seeing that state. And, because the buttons aren't in a button set, the button stays in that state, even when other buttons are selected.
Finally, hurray for you preparing a test .story file! I appreciate getting a simple file for troubleshooting. 😄
You're welcome. I also played around with the triggers in the real file and found out that by deleting the built-in Visited state, it also works.
As far as the test file, the real one has probably 100+ triggers and variables and about 20 slides - it is a challenge for me to unpack, much less someone looking at it for the first time.