Forum Discussion
Trigger ordering inconsistancies bug
Hi,
The Multiple Choice task that I've designed for a huge project is experiencing some curiosities.
First of: I can't make the layers open properly if I use object states as triggers. But I circumvented this by changing a variable with object states first. And then opening the layers using that variable.
So I have two identical slides in two different storyline files. In one storyline file, a certain trigger has to come before the others, so the correct layer can be opened. In the other storyline file, this specific trigger has to come after the others, so the correct layer can be opened.
I can't share the 2 storyline files publicly. See the included picture for a full explanation.
Three things come to mind.
1. It may be that the variables arrive at this point with different values (perhaps from their default settings), and the triggers aren't changing them the way you think they should. To check it, put a text box on the slide with the contents "%mc_1%. That will show you what the value of the variable actually is.
2. If both layers are showing, the value of the variable must change between the Show layer Forkert and the Show layer Korrekt triggers, or there is some sort of corruption in the slide. There is no other way those two triggers can show both layers.
3. Sanitize those two slides (and such others as absolutely necessary), put them in a new project, and attach them here. Someone can look at them. You can sanitize them by replacing the text with a description (This text box 4), or Lorem (=lorem(2,3) Return).
I would pop some references on the slide to see the values of what you are tracking as Walt suggest.
Also I can see in one of those triggers you are validating selected and normal. All built in states will normally report them selves back as Normal, so Selected will often also Validate as Normal. Until this gets fixed it is much better to use IS NOT Selected rather than IS Normal.
Personally to make life easier I would always name objects that you reference in triggers then you can see if you made a mistake, choosing the objects.
I think you could rationalise down your Incorrect triggers to one if you use OR conditions, or a more elegant solution would be to add a trigger at the very top to set the MC_1 variable to false when user clicks that way you know it is false and then only have your trigger to change it to True if all the states are correct, flooded by the slow layer triggers, just a bit over complicated at the moment.
