Solving technology problems, one at a time
If you are having problems with applications which use liveconnect, you may find it helpful to know that there are some issues with certain updates of Java 1.6 and Liveconnect. I’ve found that sometimes installing
Continue readingWe use Captivate 3 quizzes sometimes with our Docent 6.5 LMS. Usually the quizzes have multiple parts or “SCOs” but occasionally we build one that has only one part.
Sometimes people launch a quiz but need to quit before they are done taking it, and in such cases we would prefer it be marked “incomplete” and allow them another chance to take the quiz. Usually we would also prefer any failed quiz to be allowed to be retaken.
But, by default, Captivate sees any failure to reach the mastery score as completions.
There is an easy fix,
suggested by Franck Buland on the Adobe Captivate forums
– simply modify the [project].htm file at lines 95, 96, 97.
Continue readingJavascript is a loosely typed language, which means it is possible to define a variable without specifying what type of data it holds (string, integer, floating point, etc.). This can cause problems if you think a particular value is a number when in fact it is a string. A string must be converted to a number to use it in calculations.
For example, when working with SCORM elearning software, scoring and performance data is stored in a Learning Management System as strings. If you need to do calculations with the data after retrieving it, the string data must be converted to integers or floating point type.
The parseInt() function can be used for this purpose. It parses a string and returns an integer. However use of the function without understanding the details can lead to unexpected results. If your string begins with a zero, the number will be evaluated in octal instead of decimal system. In Octal, 08, 09 are not valid numbers, and 010, 011, etc. will not represent the same values as they would in decimal system.
Continue readingSeveral branching functions are included in js/branchingToolkit.js and are available to be used in your modules. Note: These haven’t been thoroughly tested!
The css styles are defined in several sheets. Any of the styles can be overridden by adding a new definition for the selector to /css-local/userStyles.js or to individual pages or even individual elements on a page. YOU WILL NOT BE ABLE TO change any of the files inside the css/ folder but you can add your own overrides to userStyles.css.
Continue reading Here’s a screenshot of the template, showing part of the left-hand navigation expanded. Note the previous/next navigation buttons at upper right, which are automatically created based on your list of pages, as is the progress bar and page numbering at upper right. |