I have a text entry field in a simulation where the user is required to enter a line of text. I want a layer (showing an error massage) to trigger if the text entry is not equal to two options. It works with one option but not with two. I've attached an image of how the trigger looks. It does not seem to like the 'not equal to' value being used more than once in the conditions.
This trigger will always fire. Even if the user enters one of the acceptable answers, it will not be equal to the other (assuming they are different; hard to tell from the picture), and will show the try again layer.
Join them with is not = AND is not equal. That way, if the answer is equal to one of them, it won't show the try again layer.
CAVEAT:This is just a guess; it's hard to be sure without seeing the .story file.
That is what he was referring to. Using the same 'not equal to" condition in an OR statement will create a scenario where the trigger is activated every time. His suggestion is to change it to an AND statement.
4 Replies
This trigger will always fire. Even if the user enters one of the acceptable answers, it will not be equal to the other (assuming they are different; hard to tell from the picture), and will show the try again layer.
Join them with is not = AND is not equal. That way, if the answer is equal to one of them, it won't show the try again layer.
CAVEAT:This is just a guess; it's hard to be sure without seeing the .story file.
This post was removed by the author
Thanks Walt. The only difference between the two options is a full stop at the end of one of them.
Can you explain what you mean by "join them with is not = And is not equal"? Are you meaning to change the AND/OR option to AND rather than OR?
PS The .story file is quite large which is why I didn't attach it.
That is what he was referring to. Using the same 'not equal to" condition in an OR statement will create a scenario where the trigger is activated every time. His suggestion is to change it to an AND statement.
yes, David's right
This discussion is closed. You can start a new discussion or contact Articulate Support.