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 trigger State.
When all drag objects are on a drop object, none of them has the status Normal. So a trigger When none of or When all are not should do the job.
In the attached project you see that differently completed Trigger Wizzard forms are leading to the same trigger, but different (unexpected) behavior of the Submit button.
You can view the output on https://360.articulate.com/review/content/7ec5c9d8-8d08-4f40-8d19-924910130af9/review
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.
It seems I am not the only one with this problem: https://community.articulate.com/discussions/articulate-storyline/triggers-when-state-of-is-not-working-as-expected
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.
You can do it but it needs more work. Even a custom state would not work which I am finding very odd.
I did it will variables (this is something I hate to do). But seems to work fine, it is just more triggers and more work.
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.)
Hi Phil and David,
Thank you for searching for a solution. The project is for one of my customers and I do not want to bother them with variables.
It is strange that On state works on states of the drop objects but not on the drag objects. Davids solution can only be used for one drag object on each drop object.
I will ask Articulate support to have a look and determine if this is perhaps a bug.
Case: #01898016
Gerald Sale from Articulate Support wrote this:
I found out that the change of state trigger is not firing correctly if it is referred to object Normal state in Freeform Drag and Drop question.
I’ve logged it as a possible software bug.
@Gerald: Thanks for your help so far
Thanks for reaching out to the support team and sharing an update here, Chris.
This conversation is now linked to the report so that we can share any updates with those following along here as well.
This issue is related to https://community.articulate.com/discussions/articulate-storyline/triggers-when-state-of-is-not-working-as-expected. I got a message that the issue was solved.
I tried it, but is still persists for drop objects.
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.
