Have you noticed that when you put a web object or HTML5 Animation in your project, it ignores the layering within the Captivate timeline and the object always appears over your Captivate content. This video will show you how fix that issue.
I use web content a fair bit in my projects. It’s either a HTML5 file or an Adobe Animate interaction saved as an OAM file. Sometimes though I have an issue in the fact that the web object ignores the layering within the timeline. It seems to be playing “Direct to Screen”.
The reason for this is because it seems the default is that the web object is placed inside an iFrame. It’s possible to edit the rendered HTML file and fix that but that’s not practical. You’d have to reedit the HTML 5 every time you published.
This video will show you a neat hidden feature on how you can edit the Adobe Captivate configuration file that will allow you to layer web objects.
Hidden? Official Help document mentions this hack:
https://helpx.adobe.com/il_he/captivate/user-guide.html/il_he/captivate/using/web-objects.ug.html
Scroll to the topic ‘Things to consider when using Web Objects….’
I have answered this editing workflow many times in all social media, and I am for sure not the only one having done so since years. There are many YouTube videos around as well about that topic. It has several drawbacks as well. In many browsers the interactivity will be lost when following this workflow with UseWidget7. It can be solved with JS as you can read in this post by a great JS expert, David Crawford. However not appropriate for new users:
Sorry, Phil, but expect more interesting topics from you. Like how to interact between an OAM and Captivate. At the moment I am use CpMate or CpExtra for that purpose, but not everyone has those widgets in their toolset.
You must be logged in to post a comment.