Forum Discussion
FORCED_COMMIT_TIME value of 60000 (60k)
Thanks Phil. I know we can change the value (a simple edit to the js file) and why you may not want to set the value too high or low. I'm just questioning whether it is actually being used by the course and if it is, whether it is treating the units as milliseconds.
The reason I question it is because I can't see anywhere where any JavaScript actually reads this value and the rate of LMSCommit() don't seem to tally with the value set.
Okay, I think I can give a clearer example of the problem.
I have an LMS-published SL2 course with default configuration.js settings including FORCED_COMMIT_TIME=60000 (60000ms = 1 minute)
On my LMS, whenever an LMSCommit() call is raised by the course, I log the time into a log window. I run the course and let it sit idle.
My log looks like this...
...
LMSCommit()
Time=10:42:51
...
LMSCommit()
Time=10:52:52
...
LMSCommit()
Time=11:02:52
...
LMSCommit()
Time=11:12:52
...
Clearly 60000ms = 1 minute does not equal (11:12:52 - 11:02:52) = 10 minutes, so either SL2 is incorrectly interpreting the 60000 as 60000 hundreds of a second = 10 minutes or it is ignoring the value completely and using a default/hardcoded value (which is what I suspect as I cannot see any other reference to FORCED_COMMIT_TIME in any other Javascript file in the course)).
Is there a means for me to raise this with Articulate at a technical level?
Thanks,
Chris
