I am building an interaction in which the learner has to sort rectangles onto two photos. The images change depending on which image a rectangle is dropped on. I did this with variables. (see image attached)
At first, I was able to adjust the variables before changing the state of the images. However, all of a sudden my variable adjustment triggers come last and the others first. I can't move the triggers beyond the lowest state change trigger. (see up-arrow being inactive in screenshot)
Are you able to share the project here with folks? If so, upload a copy of your .story file and then folks in the community and staff can take a look at exactly what's going on and help within the file. It's often difficult to tell from a screenshot alone what exactly is happening.
If you'd prefer to share the content privately, no worries! Our Support Team is standing by too - and they'll delete your file when done testing to adhere to our data and privacy standards.
Sure, see the slide attached. I have other slides that allow me to move the triggers freely, as was the case with this one at first. But sometimes Storyline semes to restrict the distribution of triggers. You can also notice that the 'Add' triggers can't be moved ahead of the 'subtract' triggers and both can't be moved up before the 'change state' triggers.
The slide in question is attached two replies above if you'd like to take a look.
Why would you not be able to change a state before adjusting a variable? I actually have other slides built where I do just that. I can drag and use the arrows, but only up to the point of where I start getting into the state change territory.
Mind you, at first I had the add/substract triggers before the state change. once I moved them after the state change I somehow lost the ability to move them before the state change again.
I'm not sure what I'm missing. As I said, I have other slides where this is not an issue and I can't see what would make this slide different. :S
"You have a trigger that says change state if A is dropped on B or C
Then a trigger that says adjust variable if A is dropped on B
These triggers are not related as the second trigger has nothing to do if you drop on B"
I assume you meant it has nothing to do if you drop on C?
Either way, thank you so much for replying. I was able to make the slide work now, though I now have not just 1000 triggers, but 2000 on the slide. :D
Still think the triggers should work independently from each other, but I guess that's a programming issue and it's probably related to how triggers are built-in programming. Maybe something for Articulate to think about in future releases?
14 Replies
There are no attached screenshots...?
Oh, thanks! Updated the post.
Nobody? :(
Hi Niels,
Are you able to share the project here with folks? If so, upload a copy of your .story file and then folks in the community and staff can take a look at exactly what's going on and help within the file. It's often difficult to tell from a screenshot alone what exactly is happening.
If you'd prefer to share the content privately, no worries! Our Support Team is standing by too - and they'll delete your file when done testing to adhere to our data and privacy standards.
Sure, see the slide attached. I have other slides that allow me to move the triggers freely, as was the case with this one at first. But sometimes Storyline semes to restrict the distribution of triggers. You can also notice that the 'Add' triggers can't be moved ahead of the 'subtract' triggers and both can't be moved up before the 'change state' triggers.
Can someone from Articulate at least tell me if this is the expected behaviour of if we're looking at a bug?
You are changing state before subtracting, without seeing your project this looks like expected behaviour.
Trigger order is important. You can drag the trigger using handles on the left pf the trigger if the arrows don't work (that maybe a bug).
Thanks for the reply Phil.
The slide in question is attached two replies above if you'd like to take a look.
Why would you not be able to change a state before adjusting a variable? I actually have other slides built where I do just that. I can drag and use the arrows, but only up to the point of where I start getting into the state change territory.
Mind you, at first I had the add/substract triggers before the state change. once I moved them after the state change I somehow lost the ability to move them before the state change again.
I'm not sure what I'm missing. As I said, I have other slides where this is not an issue and I can't see what would make this slide different. :S
Cannot see an attachment. It may be the arrows that are not working you can drag and drop the triggers if the arrows are not working
Let me attach it again to this message.
The arrows and drag/drop have the same limitation. I can't drag it up any further than the arrows allow me. :(
Ah! I see this is because your changes state trigger works on two drop targets whereas your subtract only works on one
Hm... not sure I understand the logic behind this? Why would the number of drop targets determine the order of triggers?
The drop targets are like conditions in this case.
You have a trigger that says change state if A is dropped on B or C
Then a trigger that says adjust variable if A is dropped on B
These triggers are not related as the second trigger has nothing to do if you drop on B
If however you have:
change state if A is dropped on B
adjust variable if A is dropped on B
Then you can move the order around because they are analogous
It is odd and I think I would expect to be able to move them around, but I can also understand the logic.
"You have a trigger that says change state if A is dropped on B or C
Then a trigger that says adjust variable if A is dropped on B
These triggers are not related as the second trigger has nothing to do if you drop on B"
I assume you meant it has nothing to do if you drop on C?
Either way, thank you so much for replying. I was able to make the slide work now, though I now have not just 1000 triggers, but 2000 on the slide. :D
Still think the triggers should work independently from each other, but I guess that's a programming issue and it's probably related to how triggers are built-in programming. Maybe something for Articulate to think about in future releases?
This discussion is closed. You can start a new discussion or contact Articulate Support.