Bug in SL2 "between two values"
Jan 19, 2015
I believe I've found a bug in SL2 but wanted to post here to see if I am mis-interpreting something.
I have a few triggers set up to evaluate a javascript value when a button is clicked. The value is passed into the course when it first loads and this works no problem.
In my first screenshot you can see my triggers and they use the "between two values" option in the conditions. On the first trigger I have this setup to go to Slide #1 if the value is between 3 and 7. That means if the value is either 4, 5, or 6 the course will send me to Slide #1.
The second trigger is configured to fire only if the value is between 6 and 10. That means it will fire if the value is 7, 8, or 9.
If I pass in 4, 5, or 6 the first trigger fires as expected, sending me to Slide #1.
If I pass in 8 or 9, the second trigger fires as expected, sending me to Slide #2.
The bug is when I pass in a value of 7. 7 is NOT between 3 and 7 which is the Condition of the first trigger.
When I pass in 7 I am expecting the 2nd trigger to fire because the Condition there is that the value is between 6 and 10.
When I pass in 7, the FIRST TRIGGER fires! I believe Articulate has a bug with how it does its comparisons on the top end of the "between two values" condition. I think it is doing a "less than or equal to" comparison when it should simply be doing a "less than" comparison.
If I change my ceiling value in the first trigger to 6 everything works as expected, but technically that shouldn't work. Hence, my bug report.
Anyone had this problem? Am I confused? Has this bug been reported?
5 Replies
That does sound like a bug. The less than, greater than, less than or equal to, greater than or equal to, and between two values are tricky sometimes to get them to behave correctly. Although I've not used those with JavaScript before.
Whether this a previously reported bug or not, I'd recommend submitting it along with a sample .story file.
Off hand, the only alternative I can think of is a trigger that locks into each specific value. For example: Jump To Slide #1 *IF* value is 6 OR 7 OR 8 rather than a less than or between.
Thanks Kevin. I have the workaround working as I mentioned above, it's just a pretty glaring bug that should be easy to replicate.
Is there a link to report bugs for SL2?
Hi Marty,
You can always share here in the forums (staff monitor the forums and respond to technical support issues) or connect with our Support engineers here.
You'll want to share a copy of the .story file either way - and since we're unable to assist with Javascript elements you may first want to check if using the "between" with two numeric variables that are set not using Javascript exhibits the same behavior. If not, you'll want to look further at how you set up the Javascript.
Attached is definitive proof of this bug. No javascript being used, I just created a project variable called TestVar and set its default value to zero.
In this storyline file I have 6 buttons setup. clicking any of them will set TestVar to the number value on the button.
When ready click Evaluate TestVar to run the triggers. All will work as expected except for 7. By the conditions of the triggers a value of 7 should take you to Slide #2. But as you will see, it takes you to Slide #1.
7 is NOT between 3 and 7 YET the first trigger on Button 7 seems to think so!
Please verify and escalate this bug!
Hi Marty,
Thanks for sharing that sample file here. I see the behavior you mentioned in terms of the "between" condition, so I'll be sharing this with our Quality Assurance team. In the meantime, it seems that you're able to utilize the "greater than" and "less than" triggers to have it work as expected.
This discussion is closed. You can start a new discussion or contact Articulate Support.