Second image showing next to slide? Footer not working?

[JoNHi]

Hi everyone,

I'm doing some edits on a Captivate 8 file for a client. This file was created by someone else who I don't have access to now. They've done something with a footer that I haven't seen before. Here's what I can see:

In Captivate:

The left side is the slide and on the right there seems to be a second version set up and that one is slightly bigger and has the footer which shows when it was published. Like this:

When I publish it, there's not footer showing. It looks like the slide part I mentioned above.

Has anyone come across something like this before? Is there a setting I don't have that will make that footer show? What's the reason behind putting it in the side of the slide, rather than in a master slide?

Thanks

Jo

[Lilybiri]

IFirst idea, probably not correct: it looks like a custom playbar. Did you check the Projecr, Skin editor?

Sorry, didn't look closely enough at the first screenshot. That image to the right is in the scratch area. I wonder if it has perhaps an Effect attached to if?

Could you select that image or group to the right in the scratch area, and show it in the Timeline? Do you have advanced actions that apply an Effect to that group or image? Effect could have been to move on the slide, or to cover the slide after all audio has been listened to. You can have a look in the Advanced Interactions panel (F9). Effects have changed in CP9.

[JoNHi]

Hi Lilybiri,

I'm not able to select any of the times and they don't show on the timeline. They aren't on every slide either. Another thing to mention is that in the published version it has a progress indicator that you can click on to take you to different parts of the module, like a menu. But I can't see anything in the TOC section.

Edited to add: I think the images I can see to the side of the slide isn't actually connected to what I see on the published version because there's not glossary button but on the published version there is. It looks very much like a skin that's been added but I don't know where that could have come from if it's not in the skin editor.

[Lilybiri]

The image is there on that particular slide, it should be visible on the timeline even though it is in the scratch area. It is probably not timed for the rest of the project, that is why I was suspecting it would be moved on the slide based on an advanced action.  Did you check the Advanced Interaction panel? The glossary button can have been added on a master slide, it doesn't need to be part of the image you have in the scratch area.

If it is a skin, you should see a reference in the Skin editor.

[RodWard]

This is just a wild guess, but...Is it possible the original developer was NESTING this project inside another Captivate project AFTER publishing it out and that's why you cannot find the navigation buttons anywhere?

Perhaps the image that is currently sitting in the scrap area was intended just as a guide so that he could see where everything was going to end up in the parent project.  Maybe you're only dealing with ONE part of this equation and somewhere else there is another CPTX into which these published projects were inserted.

[JoNHi · Accepted solution]

Hi Lilybiri and RobWard, I have finally got my answer tonight! He used code to add it. God knows why! It has definitely made my life more complicated but I have finally got it all working beautifully in an updated module and also a new module. I had to add code to the index.html file and also copy in and edit some addition css and js files. Thanks for your help! If nothing else it made me feel better that even the experts like you guys were a bit lost at my situation!

[Lilybiri]

How could we have known that JS or CSS was embedded in the HTML-files? Maybe I should have asked for it, but this is bit outside of issues within Captivate. Its flexibility allows to embed JS,  either in the companion JS-file or HTML-file.

[JoNHi]

I didn't even know that was something that could be done so it's been interesting for me. I'm not sure it's something I would bother doing as I feel like the menu could have been replicated within captivate but it's good to know that there's something further that can be done using js and css.

[RodWard]

Since this issue proved to cost so much time, and since you might not end up being the last person to touch this project, I suggest you take mercy on the next victim and fully document how this effect was achieved.  Make sure that information travels with this project somehow. 

Perhaps you can put it on a slide in the CPTX and hide that slide so that it doesn't appear in the published output but the next developer will still see it.

[JoNHi]

Yes that's actually exactly what I've done. I've put a hidden slide at the end of the module and added the steps I had to do once I had published the module. I'll keep doing that with all the modules in this project so they can be stand alone edited as well.