Trigger an action if state 'is not' Normal

Oct 10, 2022

Hi, Has anyone had an issue when using 'Is not' to trigger an action in the Change State trigger. So for example change the state of a button from hidden to show if three other objects on the same slide are no longer in the Normal state i.e. Change state of next button to show if 'all' object 1, object 2 and object 3 'Is Not' 'Normal' (see attached image). 

In this example the three objects may not have the same state e.g. visited, as they do different things/have different states which are checked by other triggers. 

This has worked in the past however I have just opened a project to update the content and the 'Is Not' feature is no longer working.

I'm currently running Storyline 360 version V3.68.28820.0

Trevor

 

 

 

 

 

7 Replies
Walt Hamilton

As the trigger is written, if any button reports itself as "Normal", the trigger fails. The problem is that "Visited" (and I think all the states that show in the drop-down list) are like most of us; they think they are normal. So when asked if they are Not Normal, they say "False, I am Visited, which is a normal state."

I suggest you write the conditions as

if button1 = Visited AND button2 = New State, AND button 3 = OtherState. if you know what state you are looking for.

Another option would be to give all buttons a custom initial state, like NewNormal, then substitute NewNormal for Normal in the trigger as written, and it would work.

Hannah R Conner

I am having a lot of issues with this as well. I noticed it maybe a year ago when updating projects that had worked in the past using triggers based on "is not normal". It DID work in the past and really SHOULD work - there's not an easy substitute for this trigger, especially in previously developed projects that relied heavily on it. It's a real problem - I can't republish anything old and be certain it will still be working. 

Trevor White-Miller

Hi Hannah, I agree the 'is not normal' is a very useful build method which reduces the alternative programming steps in some particular situations.

And yes it did used to work and I have to be very careful when opening previous projects to find if 'is not normal' was used somewhere and change to avoid an issue. 

I'll log it as a SL360 bug and see what Articulate say about it.