Actually, the trigger to set next to normal at 22 seconds is missing. The current trigger only fires when the timeline starts, and will work when the slide is revisited, but not the first time.
Since the normal and disabled states look the same on the slide, I don't think you need to mess with the state. The condition on the next button will do everything you want. The only need you have of changing states on the next button is to give the user a visual clue that it is now active.
My personal philosophy would call for the next button to be hidden until it is active. (Little irritates me more than an obvious button that I cannot click!!). In that case, you need the trigger to change the state of next.
Hi Walt - thanks for replying - but it is that visual queue that I want. Whether the initial state of the button is Hidden or Disabled is irrelevant (although you have raised a very interesting point there!)
Hi Phil - thanks for this. Is the only thing you changed the Cue Point rather than the trigger on 22 seconds? It seems to work great but I don't understand why your works and why mine didn't!
The Next button colour was a mistake, the properties hadn't copied across onto that example. The Normal state of the button is red, and the Disabled state grey.
Your version didn't work because the trigger to set next to normal at 22 seconds is missing.
Phil added it, so his works. He uses cue points rather than static times because his interactions frequently have a lot of activities. If you trigger several actions at once, it is easier to come back and change them by moving one cue point than it is to change a time on each of them.
Glad that Walt and Phil were able to assist you here -just wanted to pop in as one of your posts got flagged as potential spam - so I unflagged and you should be good to go.
9 Replies
Actually, the trigger to set next to normal at 22 seconds is missing. The current trigger only fires when the timeline starts, and will work when the slide is revisited, but not the first time.
Since the normal and disabled states look the same on the slide, I don't think you need to mess with the state. The condition on the next button will do everything you want. The only need you have of changing states on the next button is to give the user a visual clue that it is now active.
My personal philosophy would call for the next button to be hidden until it is active. (Little irritates me more than an obvious button that I cannot click!!). In that case, you need the trigger to change the state of next.
Hi Walt - thanks for replying - but it is that visual queue that I want. Whether the initial state of the button is Hidden or Disabled is irrelevant (although you have raised a very interesting point there!)
So I'm afraid I'm still a little confused here...
Hi Ant, I think this works, your main issue is your Next button normal state is grey so you will not see it change colour.
Just a little thing but I would cut off that breath sound at the beginning of that slide
Hi Phil - thanks for this. Is the only thing you changed the Cue Point rather than the trigger on 22 seconds? It seems to work great but I don't understand why your works and why mine didn't!
The Next button colour was a mistake, the properties hadn't copied across onto that example. The Normal state of the button is red, and the Disabled state grey.
ps. I hadn't heard the deep breathing! Thanks for the heads up!
I added another trigger at 22 seconds as well.
I prefer cue points because if you have to change the audio or cut a bit off then you can drag the cue point to the new spot.
Your version didn't work because the trigger to set next to normal at 22 seconds is missing.
Phil added it, so his works. He uses cue points rather than static times because his interactions frequently have a lot of activities. If you trigger several actions at once, it is easier to come back and change them by moving one cue point than it is to change a time on each of them.
OK guys, that all makes sense. Thanks very much for the support.
Hi Ant,
Glad that Walt and Phil were able to assist you here -just wanted to pop in as one of your posts got flagged as potential spam - so I unflagged and you should be good to go.
This discussion is closed. You can start a new discussion or contact Articulate Support.