Comparison of 2 numbers does not appear to be evaluating correctly
Feb 14, 2017
Hi,
I'm new to Articulate and have just downloaded Storyline 360 to evaluate. On creating a project to evaluate a sequence of numbers, I kept on getting errors. I've simplified the issue in a .story file that compares 2 numbers entered into 2 number fields. The comparison is: Is number1 < number2. I worked out the answer in 2 different ways to try and test this issue, both of the ways use basically the same logic, but sometimes the answers come out incorrectly, and sometimes different answers are produced by the 2 different methods. I get the following results:
Set number1 = 6 and number2 = 12. This gives me Answer1 = No and Answer2 = No.
Set number1 = 1 and number2 = 12. This gives me Answer1 = Yes and Answer2 = Yes.
Again, set number1 = 6 and number2 = 12. This gives me Answer1 = Yes and Answer2 = No.
I've attached a screenshot, and the triggers and variables used. Together with the .story file.
I would like to know if anyone else is getting the same results, or if anyone can explain why it is behaving as it is (or what I'm doing wrong!).
Many thanks for your help,
Pete
14 Replies
Hey Pete - Thanks for sharing your file and allowing me to take a look. I do see the behavior you are reporting, but it seems to be due to the Variable you've set for the ResultFlag1 - you have the answer 1 dependent on it in your file, but nothing ever adjusts this value back to the default of false, so it will always equal True once it changes in your course.
I think you can set this up without this dependency. I deleted that in your triggers and set up answer 1 similar to answer 2. See if this is closer to what you are looking for in the attached.
Hi Leslie,
Thanks for your reply and for pointing out that I'd not reset the ResultFlag1 variable back to false. I'm still confused though why the condition does not appear to be evaluating correctly when I enter "6" for number 1 and "12" for number 2..... 6 is less than 12, but I'm getting the Answer1 = Answer2 = "No" when it should be "Yes"?? Do you get the same result (i.e. "No") when you enter the numbers "6" and "12"?
Many thanks for your assistance. Peter
Hi Peter
i did some testing last night on your file and noticed the same - regardless of whether you use the result flag variable or any other combination of triggers the answer for me was always incorrect. Unfortunately my internet connection went down when I tried to post my reply. I'm out of my office at the moment so can't upload the test file I was playing with but can do so later if you like.
Hi Wendy, Thanks for your reply. If you are able to provide a test file where the number 1 < number 2 evaluation provides the correct answer for all numbers that fit the condition I'd be interested to see it. The number 12 seems to be a problem number for me for some reason.
Thanks, Peter
Hi Peter,
see attached sample file. It doesn't matter which logic we use, variables or in my example a mix of variables and states there is a bug.
If the number on the left has less digits than the number on the right or vice versa - the logic does not work
If the numbers on the left and right have the same number of digits - the logic works.
eg: 1 and 9, 30 and 20, 121 and 150 - all work.
I'm going to do a test in SL2 and see what happens
Hi Wendy. Thanks for checking this - I'd be interested to learn what happens in SL2. I'm sort of glad that someone else has been able to reproduce this issue - I was pulling my hair out for a while there thinking that I was missing something obvious. Peter
SL2 is fine - see sample attached.
Now lets go a step further:
SL2 previews in flash and SL360 previews HTML5. I'm going to publish both to my server and test again - it may be a HTML5 issue.
Stay tuned.
I've just tested my original project in flash and the logic performs as expected, so I think you may be correct with your deduction that it's a HTML5 issue. Peter
Here are the test files published to web and uploaded to server. It's isolated to SL360 HTML5 version
SL360 test
FLASH version: - Correct
http://www.fuziondezign.com.au/Forum%20uploads/Feb2017/TestNumberCheck/NumberCheck-SL360-WF%20-%20Storyline%20output/story_flash.html
HTML5 version: - Incorrect
http://www.fuziondezign.com.au/Forum%20uploads/Feb2017/TestNumberCheck/NumberCheck-SL360-WF%20-%20Storyline%20output/story_html5.html
SL2 test
FLASH version: - Correct
http://www.fuziondezign.com.au/Forum%20uploads/Feb2017/TestNumberCheck/NumberCheck-SL2-WF%20-%20Storyline%20output/story.html
HTML5 version: - Correct
http://www.fuziondezign.com.au/Forum%20uploads/Feb2017/TestNumberCheck/NumberCheck-SL2-WF%20-%20Storyline%20output/story_html5.html
Hi Wendy. I really appreciate your assistance with this. I'll report the bug. Regards, Peter
No worries Peter, let's hope they can push a fix out quickly.
Hi Pete. Thanks for working with our support team! I see your case with Ryan (1015006), and it looks like he shared his and your findings with our QA team for investigation. This discussion is tagged for an update when we get one.
Wow! Thanks for all your help with identifying this issue Wendy and for getting that reported Peter :) Looks like it's been shared with our QA Team - great teamwork.
Hi everyone! We just released another update for Articulate 360, and included a few important fixes and new features that you'll see in the release notes here.
We fixed some triggers that didn't always work correctly in HTML5 output, including triggers that execute when clicking outside an object, key-press triggers, and conditions that compare two numbers.
Just launch the Articulate 360 desktop app on your computer and click the Update button for each application.
Let me know if you have any questions, or feel free to reach out to our support team!
This discussion is closed. You can start a new discussion or contact Articulate Support.