Copy link to clipboard
Copied
Hello All -
The graphic designer for my project has created some simple interactive Edge OAM files, but when I import them in to Captivate and publish the project, the on-screen clickable buttons that should activate text for a topic are not working. Is there a way to overcome this so a student can click on the buttons and they will "play" (activate the text associated with them)? There is no audio associated with the buttons. Maybe the button needs some sort of specific coding within Edge? Or maybe I need to import the OAM file a different way. I'd appreciate any assistance you can provide.
Copy link to clipboard
Copied
An OAM is an animation, there is no easy way for communication between Captivate and the OAM, besides using JS maybe.
Why do you need to create buttons in OAM? Aren't the buttons in Captivate with all their functionality insufficient?
Copy link to clipboard
Copied
Yes, the first part of the OAM is an animation. The animation ends with interactive buttons displaying on the screen. I'd like those interactive buttons to be functional within Captivate. When the same Edge file is published differently (to work with a custom HTML template) the buttons do indeed work. So, it's just when the Edge file is published as an OAM and placed inside Captivate that the buttons aren't working. Now, I'm not a programmer, but if someone could explain how to fix this (maybe using/altering JS with Captivate), then I could get the graphic designer or a programmer to play with it and see if we could get it to work. I just need a starting point. I had thought we'd tested this before on another project (that we eventually opted for a custom template over Captivate due to some limitations of Captivate) and the buttons in an interaction worked, but then I remembered we were using Captivate's Blank Project format. So, then I got to thinking maybe that's the difference. Unfortunately, I don't have committed programming resources for this project so I have to borrow and thus a starting point would be helpful.
Copy link to clipboard
Copied
There are a few things that you can check. Is the Web object after you import the HTML5 animation at the top of the timeline stacking order?
Is there an element in the project that is hidden that would cover the animation?
Check your C:\Program Files\Adobe\Adobe Captivate 8 x64\AdobeCaptivate.ini
Make sure that the following line is set to 0.
UseWidget7 = 0
Copy link to clipboard
Copied
Thanks for the ideas. We will check them out. I actually do use click boxes on most screens to stop their advancement. I didn't think to check that. I will check all these and post a response on what we discovered. I really appreciate the ideas!
Copy link to clipboard
Copied
TLCMediaDesign -
So, I removed the click box for that screen, made sure that OAM file is indeed on the top of the timeline, and went to the AdobeCaptivate.ini file and the line referenced is indeed set to 0. I published the file again and yet the buttons still do not work. However, I did notice the following that I did not make note of previously (it may have been a fact and I just didn't notice):
Wrt your one suggestion "Is there an element in the project that is hidden that would cover the animation?" - I'm not sure. Is there a way to look for hidden elements within a project that could affect this? What types of things might I be looking for? I'm fairly certain there is nothing on the slide with the OAM that is hiding it. There is only the audio file, the actual slide, the title of the page and the OAM file itself that comprise that particular slide on the timeline (and again OAM is on top). Could there be some setting for the buttons within the OAM file that needs to be changed/recoded slightly.
Copy link to clipboard
Copied
I was suggesting that something may cover it because I have a similar instance when using a lightbox type element. On a quiz slide with radio buttons, you cannot click on the buttons, even when the lightbox is hidden. I believe this is because it's a martshape and is turned into a canvas element, which creates z-index issues.
I would publish, the go into the wor folder, find a wo_#### folder and see if the oam file runs there. It should be an html file.
Copy link to clipboard
Copied
Hmmm, so I didn't realize that that OAM file showed up there (though having messed with similar Articulate packaged folders, I should've known that). Anyway, no it didn't play there correctly either. I tried renaming that particular html file and then copying in the HTML version that is running in a custom template, but that didn't solve the issue either. However, maybe I just need to find the correct thing to replace from the working version in the custom template with the version that's in the wor folder. I'm up for playing around with that.
I'm also having the graphic designer check some of the previous things you referenced within the actual Edge file. If somethings over the buttons in the actual Edge file that could be the issue too (though it's odd that it's working in the custom template). If something was over the buttons, you'd think that it also would not work in our custom template either. Anyway, figure it can't hurt for her to check. We have pause and rewind buttons that are also currently displaying (we generally hide those when there's no audio in an Edge file), so I've asked for those to be inactivated as well. Figure those could be affecting the OAM file differently than the custom template. I've never used lightbox, so I'm not sure about that, but it does seem like your experiences with that are providing good ideas for testing wrt the OAM/Edge Animate file. Thanks!