On the attached, the learner needs to press on each person. This should take them to slide 1.3 or 1.4. After the media completes on slide 1.3 or 1.4, the next button should appear and go back to 1.2. Once both 1.3 and 1.4 are visited, the next button should appear on slide 1.2 and take you to 1.5. It isn't working that way. I also have a floating head on slide 1.3 I can't get rid of - PLEASE help.
Your problem with the state of the next button is occurring due to the way you have set up the trigger.
At the moment it says make the next button appear when the two states are visited. However, it should say make next button appear WHEN TIMELINE STARTS and then an IF statement to say IF states of character 1 and 2 are equal to visited. As below: Hope this makes sense!
I cant see random floating head when i open it :P
Ive attached the version ive amended if this makes it easier for you :)
Try changing the trigger on slide 1.2 that makes the next button visible from a trigger on picture4 to a slide trigger. "Change state of next button to normal when timeline starts if picture 3 is visited and picture 4 is visited."
I've attached an updated copy of the sample file I shared with you yesterday. I highly recommend that you spend some time working through this sample file and deconstructing the different elements since you seem to have a lot of questions focused on working with the next button.
In regards to the floating head - I'm not seeing just a head, but the images are smaller based on how you set up the visited state - and if the characters are looking "decapitated" or not attached to their bodies, I'd look at confirming you're using a DPI setting of 96 as detailed here.
When you return to slide 1.2, if you have visited one of the scenarios, that person is smaller, because it is now in the visited state. If you don't like it, delete the visited state.
Personally, I thought it was a clever and effective way to indicate to the user where they had been and where they should go next. Perhaps the best way to solve this "problem" is to modestly take credit for it (That's the way I planned it. :)"
5 Replies
Hi Kendra,
Your problem with the state of the next button is occurring due to the way you have set up the trigger.
At the moment it says make the next button appear when the two states are visited. However, it should say make next button appear WHEN TIMELINE STARTS and then an IF statement to say IF states of character 1 and 2 are equal to visited. As below: Hope this makes sense!
I cant see random floating head when i open it :P
Ive attached the version ive amended if this makes it easier for you :)
Try changing the trigger on slide 1.2 that makes the next button visible from a trigger on picture4 to a slide trigger. "Change state of next button to normal when timeline starts if picture 3 is visited and picture 4 is visited."
I didn't see the floating head :) sorry.
When you return to slide 1.2 both my images are small and don't take up the whole screen. That is what I talking about as far as "floating head."
Hi Kendra,
I've attached an updated copy of the sample file I shared with you yesterday. I highly recommend that you spend some time working through this sample file and deconstructing the different elements since you seem to have a lot of questions focused on working with the next button.
In regards to the floating head - I'm not seeing just a head, but the images are smaller based on how you set up the visited state - and if the characters are looking "decapitated" or not attached to their bodies, I'd look at confirming you're using a DPI setting of 96 as detailed here.
When you return to slide 1.2, if you have visited one of the scenarios, that person is smaller, because it is now in the visited state. If you don't like it, delete the visited state.
Personally, I thought it was a clever and effective way to indicate to the user where they had been and where they should go next. Perhaps the best way to solve this "problem" is to modestly take credit for it (That's the way I planned it. :)"
This discussion is closed. You can start a new discussion or contact Articulate Support.