ActionScript
While updating my CaptivateController script I noticed there have been some changes to the Captivate variables available to Captivate developers. I figured I should document them for future reference. Note that some variables available in CP3 and CP4 are no longer available. The following list should be exhaustive for CP5;
ActionScript
By popular demand, I’ve updated my CaptivateController to work with Adobe Captivate 5 (CP5). Since this is an open-source project, there’s no upgrade fee. (What? “Adobe” and “no upgrade fee” in the same paragraph?!) I kid, I kid… I’m a kidder. As you may have heard, Adobe
Adobe Captivate
If you spend any time using Adobe Captivate to create SCORM-conformant courses, you’re bound to have run into an issue or two that caused you to read some Captivate forum posts. Almost without fail, someone will mention that the solution to their problem was changing the value of the
Tips and Tricks
Someone recently asked me if it was possible to customize Captivate’s SCORM manifest to reduce the need for manual editing after publishing. In her case, the manifest needed to be edited to include SumTotal TotalLMS’s custom SCORM extensions. The answer is yes. Here’s how. Find the Captivate
Adobe Captivate
Bug fixes! The CaptivateController has been updated to fix the gotoSlideAndPlay and gotoSlideAndStop bugs. Also, gotoSlideAndPlay and gotoSlideAndStop have been edited to use standard numbering in place of zero-based numbering. This means when you want to jump to slide 4, you use mycontroller.gotoSlideAndPlay(4) instead of mycontroller.gotoSlideAndPlay(3)
Adobe Captivate
This post has been updated to reflect changes to the CaptivateController since its initial release It took me much much longer than I anticipated, but I am happy to announce the new CaptivateController utility. The CaptivateController is a JavaScript utility that helps you control Captivate SWFs as well as get/
JavaScript
Update (August 2010): I have published a new list of Captivate variables that are specific to Adobe Captivate 5. Check it out. The folks at Adobe recently published a list of Captivate 4 variables. While it’s a solid list, it’s not really a complete list. Here is a
JavaScript
As alluded to in a previous post, I’ve whipped up a simple JavaScript utility to help you control your Captivate SWFs using JavaScript. Give it a spin. The biggest selling point for this utility is that it not only contains all of the built-in Captivate ‘variable’ functionality, but it
Adobe Captivate
Note: This post covers Captivate 2 & 3; Captivate 4 introduced new problems for JavaScript interaction. You can avoid the headache of writing your own code by using the free CaptivateController utility, which works with all versions of Captivate. JavaScript can control the playback of Captivate-generated SWFs. I posted some
Adobe Captivate
Adobe Captivate 3 doesn’t have a built-in mechanism for sending quiz results to JavaScript. Here’s a workaround you may find useful. The plan The basic premise of this workaround is to hijack Captivate’s ’email report’ functionality, replacing the original email-centered JavaScript with new JavaScript. This approach was
ActionScript
There is a newer list of variables available, which includes new Captivate 4 variables. A recent post (link no longer available) in the elearning development forum (link no longer available) reminded me that I forgot to post some unpublished Captivate variables I dug up a while back. These were gathered
Adobe Captivate
Many of us use a Flash-based course interface (a.k.a. ‘player’) to load Captivate SWFs and other content. A well-known stumbling block for this kind of ‘loaded SWF’ approach has been Captivate’s lack of ActionScript support — Captivate won’t allow a user to add a simple line of