Copy link to clipboard
Copied
To make training more user friendly I’ve been using a text area widget on each slide for displaying the slide’s transcript. I’ll put an image behind the widget, group them together, and then show/hide the group with buttons. This is how it appears in the training.

I had always assumed that a user would hide the transcript before opening the glossary or other objects that display across an entire project. A recent test of a nearly finished training resulted in someone having a transcript open first and then showed the help system. Since I publish to HTML5, the text area widget gets placed above everything else which results in the following appearance in the training for when the help system is displayed.

One option is to add a hide action to the help and glossary show buttons that will hide all the transcripts should they already be open, but that’s going to be 80+ hide commands. The other option is to place the help and glossary smart shapes on every slide instead of on a single master page, but then I would have to create 80+ advanced actions for those buttons on every slide that would hide the transcript. (Which is even more work than just adding in the hide actions in the master page smart shapes)
So I’m inquiring about how other people handle transcripts and/or if you’ve found a way around this issue when publishing to HTML5.
Copy link to clipboard
Copied
It would be easy enough to write JavaScript that shows and hides. If you named the text area TA_1 to coincide with slide 1 and so on, you could write one function with an argument as the object to show and hide all others.
You would still need to attach the JavaScript to your buttons but it would make for easy editing.
Make as many hides as you need. Call myShow("TA"); in the JavaScript window to show the Text Area
function myShow(which)
{
cp.hide( "glossary");
cp.show( which+"_"+window.cpInfoCurrentSlide );
}
Copy link to clipboard
Copied
Excellent. ![]()
I created a number sequence in Excel so I didn't have to change each transcript number by hand and was able to set this up in about 2 minutes. Thanks.
Copy link to clipboard
Copied
I'm now finishing up this project and the javascript worked perfectly when I implemented it. However, now it's not working and I'm at a loss as to what would cause it to do that. I've also tested out the javascript code in a blank project and it's not working there either. I have upgraded to Captivate 9, so is it possible that Adobe changed something that's causing this to no longer function as it was in Captivate 8?
Find more inspiration, events, and resources on the new Adobe Community
Explore Now