I've created an interaction where a given user selects one of two radio buttons AND checks a checkbox to reveal a hidden text box. Simple enough, right?
One of the interactions works (the radio button that says <35) and the other (<10) doesn't. Why? What have I missed?
Hello Michael, from what I understand, the user should be able to see the text box in its normal state when they click either of the radio buttons along with the checkbox. Am I right?
If so, setting the additional conditions and else statements is not necessary to bring the text box from its hidden state to its visible state. Removing those onditions and else statements worked fine at my end.
Since the first trigger is <10 & minorWear according to the triggers' order, Storyline is executing this function while ignoring the second, which is why <35 & minorWear case isn't working.
You stated that the <35 & minorWear case worked but the <10 & minorWear case didn't, however when I checked your file, the results were quite the contrary.
So please test it without the conditions and else statements in both triggers.
Do you mean (less than 35 miles) OR (Fewer than 100 hours AND Minor Wear), or do you mean (less than 35 miles OR Fewer than 100 hours) AND (Minor Wear). Both are perfectly legitimate interpretations of the way the slide is designed. Either way, the choices can be presented in a non-ambiguous way by giving only two selectable options. Sandeep and I both are guessing it is the second.
Sandeep is also correct about the conditions. I'm not sure how all of the choices can be selected, when two of them are a button set. Buttons sets are designed to allow only one of the set to be selected at a time.
Check the New Version slide in the attached sample for an idea to make both buttons work.
Sandeep, yes removing the additional conditions allows either combination to fire, but doesn't hide the text box when Minor Wear is unchecked. And, yes my original statement about which works and doesn't - less than 35 miles doesn't, fewer than 10 hours does - is true because, as you said, Storyline is executing my triggers in the order in which they are listed: <10 first, <35 second. So, I've learned something useful about Storyline and its order of execution, thank you!
Walt, yes my design is confusing. The second case (<35 miles OR <10 hours) AND (Minor Wear) is what I have in mind. However, its depiction as conceived with two separate radio buttons AND a checkbox were intentional, and has to do with how original policy guidelines were written and how users understand them. Though I can understand how it would appear unnecessary to you: a single choice for both pre-conditions (<10 and <35).
Regardless, I solved it with the attached third slide (Revised) by making the radio buttons dumb, adding a variable, and making the checkbox responsible for displaying the conditional text. Turning the conditional text on and off with the checkbox is the important action here.
3 Replies
Hello Michael, from what I understand, the user should be able to see the text box in its normal state when they click either of the radio buttons along with the checkbox. Am I right?
If so, setting the additional conditions and else statements is not necessary to bring the text box from its hidden state to its visible state. Removing those onditions and else statements worked fine at my end.
Since the first trigger is <10 & minorWear according to the triggers' order, Storyline is executing this function while ignoring the second, which is why <35 & minorWear case isn't working.
You stated that the <35 & minorWear case worked but the <10 & minorWear case didn't, however when I checked your file, the results were quite the contrary.
So please test it without the conditions and else statements in both triggers.
Good luck!!!
Do you mean (less than 35 miles) OR (Fewer than 100 hours AND Minor Wear), or do you mean (less than 35 miles OR Fewer than 100 hours) AND (Minor Wear). Both are perfectly legitimate interpretations of the way the slide is designed. Either way, the choices can be presented in a non-ambiguous way by giving only two selectable options. Sandeep and I both are guessing it is the second.
Sandeep is also correct about the conditions. I'm not sure how all of the choices can be selected, when two of them are a button set. Buttons sets are designed to allow only one of the set to be selected at a time.
Check the New Version slide in the attached sample for an idea to make both buttons work.
Sandeep, yes removing the additional conditions allows either combination to fire, but doesn't hide the text box when Minor Wear is unchecked. And, yes my original statement about which works and doesn't - less than 35 miles doesn't, fewer than 10 hours does - is true because, as you said, Storyline is executing my triggers in the order in which they are listed: <10 first, <35 second. So, I've learned something useful about Storyline and its order of execution, thank you!
Walt, yes my design is confusing. The second case (<35 miles OR <10 hours) AND (Minor Wear) is what I have in mind. However, its depiction as conceived with two separate radio buttons AND a checkbox were intentional, and has to do with how original policy guidelines were written and how users understand them. Though I can understand how it would appear unnecessary to you: a single choice for both pre-conditions (<10 and <35).
Regardless, I solved it with the attached third slide (Revised) by making the radio buttons dumb, adding a variable, and making the checkbox responsible for displaying the conditional text. Turning the conditional text on and off with the checkbox is the important action here.
Thanks for your help!