Adobe captivate 5 scorm code#

In both cases, the data is sent via an internal queue script, which uses the waitForResponse callback function. Setting g_intAPIType to 1 means you're forcing the browser to use getURL, which is cross-browser but has a few drawbacks (including lots of clicking sounds). If you're setting g_intAPIType to 0, you're forcing the browser to use FSCommand, which isn't supported in all browsers and operating systems. This callback function uses timers, and that's probably where your problem lies. The response (if any) is relayed from JavaScript to either FSCommand or a proxy SWF (for getURL), which is then monitored internally in Captivate via a callback function. When publishing for SCORM, Captivate does not use synchronous communication methods.* Depending on the browser, Captivate uses either FSCommand or the old-school getURL method to communicate with the HTML file the HTML file then uses JavaScript to relay the data to the LMS via the SCORM API. maybe that sombody ask the right question.

Adobe captivate 5 scorm code#

Ok, I can add a lot more info, but I don't know what is really important, I'm not hoping you fix my code without seeing it, but I'm out of ideas, and need new opinions, ideas, directions. In my implementation, this function first validate the value using a regular expression, and then set the value in an object. This function takes two parameters (fieldName, value) the firstone is the name of the field to be set, and the second the new value. To understand this problem, here is a little background:Р”В¬aptivate contents (all contents really but more captivate) calls a specific function many times, the SetValue function, one of the SCORM API functions. There is a way to make this sync? I mean, to force the flash wait some way?Р”Сћ) The functions are taking longer each time they are called, for example, setValue takes 7 milliseconds the first time and 200 the last time is called. I cannot change the Flash or JS-Flash interface, because this is provided by Captivate. So, when the user see the content quickly, the function calls get more and more dealayed, and at the end, maybe the user is answering question 15, and the content is sending question 4 information. If you wait a long time at the end, or if you take the content slow, it works fine.Р”Р„fter a lot of google searches, and debugging and tracing, finally, I found two main issues:Р”РЋ) Captivate - SCORM API communication is asynchronous (is the same than flash - javascript communication).

The LMS can close the window, because the LMS opened it.I'm developing a SCORM compliant LMS, and having some problems with Captivate generated contents.Р”В«asically, the behavior is: If you see a SCO (captivate generated content) with for example 15 slides and 1 question in each slide quickly, my lms is not tracking all the 15 question, only the first 3 or 4. I answered my own question, but I thought someone might benefit from my pain. * The code below will only work if there is a parent. If(window != window.parent & window.parent & ('DoCPExit'))Р”Р„nd add the following.

So onto the solution.Р”Р‡ind Utilities.js it is in the $CaptivateInstallFolder/Templates/Publish/LMS/Standard/SCORM/default/js folder.Р”Р‡ind the following. A web training module CANNOT close a window using window.close. Fire LMSFinish.) Once you tell the LMS you are done, the LMS can cleanup the window. (odd since there are two requirements to be SCORM compliant with training, 1. The problem was primarily caused by Adobe never Firing LMSFinish. After many attempts I finally found a hook I could use.

Captivate doesn't handle javascript in version 7 the same. When you click the exit button in a Captivate Lesson that is Published to SCORM the application will not exit.