Forum Discussion
Strange behavior states in Drag and Drop Interaction
In a drag and drop interaction I want to hide a submit button until all drag objects are dropped on a target. I know it is possible using variables but I thought it is also possible using the trigge...
Hello everyone!
Good news! Today, we just released Storyline 360 Update 78 (Build 3.78.30680.0) which includes a fix for the bug where the change state trigger does not work when "state of none of <objects> is" and "state of all <Objects> is not" setting is being used.
Now all you need to do is update Storyline 360 in your Articulate 360 desktop app!
If you have additional questions, don't hesitate to reach out in this discussion or in a support case.
OK, got it working without variables. Both of them are working, but Button 2 is the way to go. I keyed off of the states of the drop objects rather than of the drag objects, and for some reason, it was happy with that. I had to set the state of the drop items when the drag items were incorrect, so obviously the colors of those should change, which I did not do. (For Button 1, I set its initial state to normal, and set a trigger to hide it when any of the drop objects have a normal state, but although it works, it just makes it more complicated.)
