SL3 doesn't treat drop correct/incorrect as state: is not normal.


Building some drag&drop interaction, and I want to make "submit" button change it's state to normal when all of the pieces were dropped somewhere (correct or not).

So I created drop correct/incorrect states, unchecked in drag&drop options "Delay item drop state ..." option, and made a trigger "Change state of submit button to Normal when all of [array of objects] state are not normal".

I run my d&d, do it, and... nothing happens. My drags change colors to correct/incorrect, so the states of the drags change and are not normal. When I make trigger "change state of dragX to state custom when dropped on [array of drops]" and then "change state of submit button to Normal when all of [array of objects] state are not normal" - everything works fine.

So it seems like Storyline treats drop correct/incorrect as state normal, when it actually changes states. Why is it so?

I can't post my .story but it's really easy to recreate.

8 Replies
Phil Mayor

Articulate staff can probably better respond to that. I don't think it is classed as a bug, the normal state is referred to as the neutral state, and all other built in states are on top of normal.

There is a workaround I think, create a state called not dropped that looks like normal and set the initial state to that and then just look for "not dropped"

Alyssa Gomez

Hey folks,

Thanks so much for bringing this to our attention. We're investigating the problem with the "is not" trigger in Storyline 3, and we'll update you as soon as we know more.

In the meantime, I would stick to using "is" triggers rather than "is not" triggers. Slide 1 in the sample file I attached is an example of what I mean. 

Mateusz Szuter

Hello Alyssa,

have you been able to investigate 'is not' behaviour?
The problem with IS trigger in this case is that I can have either Drop Correct or Drop Incorrect state. And combinations of them. So it won't work. I've came with workaround duplciating normal state and naming it otherwise and then making "is not: duplicate_normal". But still, if it could wotk with default state, would be great :)

Leslie McKerchie

Hello Inés,

The issue originally reported here has not been resolved, but it is still open with our team. I wanted to share some information on how we define bugs and how we tackle them when they occur.

We haven't seen any activity on this one in a while, so I'd like to understand what you are seeing. I want to take a look at your project file to investigate what's happening with your permission. You can share it publicly here or send it to me privately by uploading it here. I'll delete it when I'm done troubleshooting.