I have five groups. I've created five variables with the value 0. When you click on the rectangle/group it should change the value to 1. Once the value has changed the state should change. Easy enough. For some reason three work and 2 won't. Actually they do work, but the change happens before it should. I've recreated this thing over and over. It was working fine and then I woke up and it had stopped working.
I've attached the file below. Any and all help is appreciated.
I couldn't replicate the problem you are seeing. The rectangles all changed correctly as expected when I ran the preview, several times. The trigger logic looks OK. I would have located the variable increment trigger on the last slide in each scene instead of the menu slide, as then the user only gets the 'completed' signal when they have viewed all the slides, instead of for just clicking the box but that's just my preference.
The first three groups, once you click on them take you to the lessons. Once you return to the home screen the button is white.
The last two groups, once you click on the them, they turn white and then take you to the lesson. They shouldn't do that. They behave differently from the top three.
After each lesson you have to return home and then you notice the button has changed, indicating the lesson has been completed.
Yes, I can see that now. I can't see any obvious reasons for this behaviour. There is nothing in the variable advance or trigger logic that suggests why the box colour change gets preference to the slide change in boxes 4 & 5. The only thing that I see is that the rectangle numbers for the troublesome pair of boxes are not in sequence with those used in groups 1-3, so I assume you created these rectangles and groups i.e 4 & 5 later on in the development. I wonder if this is influencing the way AS is assigning trigger priority?
Regards,
Alan
Alan Baines
Head of Strategic Projects
Lonza Pharma & Bioscience
228 Bath Road
SL1 4DX Slough
Tel. : +44 0118 9775061
Fax : +44 1753 777001
mailto:alan.baines@lonza.com http://www.lonza.com
I see the behavior your describing, and as Alan mentioned I don't see anything off with your triggers either. Have you confirmed that you're working with local project files?
Also, just as a reminder the visited state will happen automatically if included as described here.
Trigger order is important, but I don't think the sequence numbers of the objects could be having an impact.
Alan, also - just as an FYI, when you reply via email your signature may be included. You can edit the post if you want to remove those elements.
The behavior you see on the final two is actually pretty normal behavior. When you use the built-in visited state it should automatically change once it's clicked. For some reason those final two have just enough of a pause (before they jump to the other slides) that allows for you to see the change.
I looked at your file and here's what I'd do (I've altered your file and attached).
1. Create a custom visited state (I named it vis).
2. I changed the variables to True False and set initial value to false (to simplify the design).
3. I changed the triggers on the menu slide to evaluate the variable when the timeline starts and change the rectangle state to "vis" if variable is equal to true.
4. I added a trigger at the end of each section to change the variable from false to true.
I hope this helps! Let me know if you have any questions.
10 Replies
Hi Cindy,
I couldn't replicate the problem you are seeing. The rectangles all changed correctly as expected when I ran the preview, several times. The trigger logic looks OK. I would have located the variable increment trigger on the last slide in each scene instead of the menu slide, as then the user only gets the 'completed' signal when they have viewed all the slides, instead of for just clicking the box but that's just my preference.
The first three groups, once you click on them take you to the lessons. Once you return to the home screen the button is white.
The last two groups, once you click on the them, they turn white and then take you to the lesson. They shouldn't do that. They behave differently from the top three.
After each lesson you have to return home and then you notice the button has changed, indicating the lesson has been completed.
Thanks for taking a look .
Yes, I can see that now. I can't see any obvious reasons for this behaviour. There is nothing in the variable advance or trigger logic that suggests why the box colour change gets preference to the slide change in boxes 4 & 5. The only thing that I see is that the rectangle numbers for the troublesome pair of boxes are not in sequence with those used in groups 1-3, so I assume you created these rectangles and groups i.e 4 & 5 later on in the development. I wonder if this is influencing the way AS is assigning trigger priority?
Regards,
Alan
Alan Baines
Head of Strategic Projects
Lonza Pharma & Bioscience
228 Bath Road
SL1 4DX Slough
Tel. : +44 0118 9775061
Fax : +44 1753 777001
mailto:alan.baines@lonza.com
http://www.lonza.com
Yeah, I created those later but they were working and then they stopped for no reason I can determine
Sent from my iPhone
Hi Cindy,
I see the behavior your describing, and as Alan mentioned I don't see anything off with your triggers either. Have you confirmed that you're working with local project files?
Also, just as a reminder the visited state will happen automatically if included as described here.
Trigger order is important, but I don't think the sequence numbers of the objects could be having an impact.
Alan, also - just as an FYI, when you reply via email your signature may be included. You can edit the post if you want to remove those elements.
Hi Cindy,
The behavior you see on the final two is actually pretty normal behavior. When you use the built-in visited state it should automatically change once it's clicked. For some reason those final two have just enough of a pause (before they jump to the other slides) that allows for you to see the change.
I looked at your file and here's what I'd do (I've altered your file and attached).
1. Create a custom visited state (I named it vis).
2. I changed the variables to True False and set initial value to false (to simplify the design).
3. I changed the triggers on the menu slide to evaluate the variable when the timeline starts and change the rectangle state to "vis" if variable is equal to true.
4. I added a trigger at the end of each section to change the variable from false to true.
I hope this helps! Let me know if you have any questions.
Mike
Yes, I'm working on my local drive. I've tried to figure this out for a day now. It's frustrating because it was working and then it just stopped.
Thanks a million. Learning something new everyday. I'm just glad that it wasn't something small I was over looking. Thanks again
That's what we're here for! Just let us know if we can be of further assistance!
This discussion is closed. You can start a new discussion or contact Articulate Support.