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.
Is not normal is a difficult one to use, most of the built in states are built on top of normal and will validate as normal.
Sometimes it helps to set the initial state as a custom state and validate from that.
Hi Phil,
I was playing with this yesterday, and tried that myself, and it still did not work. Also set some variables based on the states of the drag objects, and could validate that they changed, but could not find any way to make the triggers run to change the states of the Submit buttons.
