I am working in CP7 and I haven't seem to run into this issue before. Maybe I just didn't notice...
I have several buttons on the last slide of my project. One is a shape button that is displayed for Rest of Project and opens a help caption. Another, is a click box displaying for Rest of Slide to open a survey link. Another click box to open a PDF. And then a button to Exit the course.
I noticed that when the slide ends (and the project is "over") the buttons no longer work. So if the learner were to wait until the audio finished to click anything, none of them work.
Is that normal? How can I change that?
My initial reaction was to extend the timeline, but I also don't want that to affect the learner completion. Would it? We're publishing to Adobe Connect.
Buttons typically have a "Pause after" atrribute. But you are able to turn off the pause. Have you turned off the pause for them? If so, the playhead is likely reaching the end of the slide causing them to no longer function.
I have that turned off. And yes, they stop working when the playhead is at the end of the slide. The Exit button is the only one set to "pause until clicked."
But they work just fine before the end of the slide is reached?
If so, try adjusting the pause point of the one button so it is a bit sooner. If not, you are likely encounterng the Flash Security gotcha when testing locally and you will need to configure the publish location as a Trusted Location for the Flash player.
Just a thought... How about adding a tiny invisible button on the last frame of the timeline?
I think you'll find that you need to pause the playback JUST BEFORE the last frame of the timeline if you still want these interactive objects to function. As was pointed out earlier, interactive objects usually have a pause point. The part of their timeline AFTER that pause point is usually that part where the interactive object is inactive. So ideally, you want all of your objects to remain active until there is no reason any more for the user to want to click one of them. Click boxes are often found confusing because their timeline only shows the active portion. Since click boxes are invisible anyway, the click box's pause point is actually right at the end of the object as represented on the timeline. So you usually need to pull the end of the click box object back from the end of the timeline if you want it to pause.
Sorry to pop in, just about the shape button that Kristen was pointing at. Shape buttons can be used both timed for the rest of the project or on master slides. Both have advantages and disadvantages, concerning the pause (more details in http://blog.lilybiri.com/why-i-like-shape-buttons-captivate-6)
- On master slide: if you turn pausing on (Options, not Timing accordion because it is not available for master slide objects) pause will always be at the end of the slide, whatever its duration
- Timed for rest of project: if you turn pausing on (Timing accordion), you can set the timing but it will be an absolute time, will be same on each slide.
Because you cannot control the buttons on master slides, they have no ID, timed for rest of project is more flexible. If your shape button has no pause, you could hide it on that last slide and show another shape button that has a pausing point.
Thanks everyone. I'll try adding that pause tonight and see if it works.
What is puzzling (at least to me) is that you said one of the buttons had a pause. The Exit button. So instead of adding yet another object into the mix that may confuse things, I think I'd try simply adjusting the pause point for the Exit button so it pauses earlier than it does at the moment,
That makes sense, Rick. Right now, that button is set to pause until the user clicks it. I'll change that from a click box to a shape button and adjust the timing of the pause instead.
No need to change to another interactive object, just make the timeline of the click box a little shorter, Rod already made that suggestion I believe.
Oh yep, he did. I'll do that...thanks everyone!
Since you have a bunch of buttons, you'll want to used advanced actions to stop the actions from continuing. If you use simple actions the user will eventually get to the end of the timeline. I stick a widget on the last slide so i never have to worry about it. The widget pauses 5 frames before the end and if it gets less, from user using the scrubber, it always backs up and pauses.
This has been in Captivate forever, not really a bug, just a strange way of doing things. They are obviously removing the event listeners from the interactive objects since it thinks you're done with the project.
I'm actually doing all I can to prevent from adding advanced actions to my project. Compared to shared/simple actions, the advanced actions expand the size of my files, and we need to keep these as small as possible for use on tablets. Same with the widgets. I noticed the other day when I was removing advanced actions from an old project that it was decreasing the file size by 300KB with each removal of an advanced action.
Thanks for the advice everyone.
I don't think this anomoly happens in HTML5 output, only for swf. If you don't use advanced actions you better set up a bunch of pauses or limit the number of times a button can be clicked. A scrubber can always get past anything.
I'm using custom nav...not the Captivate playbar, so there is no scrubber. According to those above, a bunch of pauses aren't necessary (just one). I should mention that the original files I received from my client were the largest mess of advanced actions I have ever seen and caused an enormous amount of problems. They made everything far more complicated than it needed to be (Lieve even saw some of those files).
I've rebuilt everything to be simpler, easier to edit, and easier to use for the learners.
Kristen, shared actions don't add much to filesize as I told you explicitly. In that file, it was not the advanced actions that were the biggest problem but a lot of crap that had been added, then not used etc.
I know. That's what I just said.
Not really, there were not much advanced actions really used, because he couldn't manage them, but there were a bunch of unnecessary objects in the first place. That was what inflated the filesize, not the advanced actions.
In a course you didn't see, there were 50 advanced actions...
My point is that I want to create my course as simple as I can. If there's a simple and effective way to do it, I'll choose that route.
I always offer the easiest way if it concurs with the wishes.