I have a project where we had a number of elements launching from one slide that we wanted to ensure the learner viewed. The whole course is open, but on certain slides the next button was disabled until the state changed on all the buttons to unlock. It seems to be buggy and I'm looking for alternatives.
Support has suggested: Number Variable that'll increment its value when users complete each module. Then, use the value of the variable as Condition instead of the object's State - in which the course was originally designed.
Are there other ways you can think of that might work more consistently?
If you want to check a condition along various places in a course, then a variable(s) is the way to go. What are the issues/bugs you are experiencing? Maybe you can share your .story file here so that someone can have a closer look.
Hi Michael - I've had support look at the courses, and their suggestion was the number variable.
I had it as t/f variable to change once the state of all buttons that showed the sections changed. The bug was that the state change didn't seem to "stick" - it would work going forward (usually) but when you went backwards, after the next button was unlocked, the state changes were not applying consistently. And the suggestions to fix were all browser related. I didn't want my client's employees to have to tinker with their browser, so looking for a way that's more reliable for the end user.
Support suggested I check with the community about any other alternatives to the number variable option.
I had a similar issue once and solved it by using a T/F variable for EACH element and one master T/F variable that only toggled on the condition that all other T/Fs were true. It is very similar to what you have but you are looking at a number of variables instead of a number of object states.
4 Replies
If you want to check a condition along various places in a course, then a variable(s) is the way to go. What are the issues/bugs you are experiencing? Maybe you can share your .story file here so that someone can have a closer look.
Hi Michael - I've had support look at the courses, and their suggestion was the number variable.
I had it as t/f variable to change once the state of all buttons that showed the sections changed. The bug was that the state change didn't seem to "stick" - it would work going forward (usually) but when you went backwards, after the next button was unlocked, the state changes were not applying consistently. And the suggestions to fix were all browser related. I didn't want my client's employees to have to tinker with their browser, so looking for a way that's more reliable for the end user.
Support suggested I check with the community about any other alternatives to the number variable option.
Thanks for your input,
Holly
I had a similar issue once and solved it by using a T/F variable for EACH element and one master T/F variable that only toggled on the condition that all other T/Fs were true. It is very similar to what you have but you are looking at a number of variables instead of a number of object states.
Thanks Owen. Much appreciated!
This discussion is closed. You can start a new discussion or contact Articulate Support.