Hi Pamela,
All of the completion variables or vatiables you set in a module are empty until used or updated. Some do update on closure but the trigger is within Courselab. That is something in the module triggers it, it isn't externally triggered by in this case closing the browser window.
Closing using the exit button of a browser (rather than the modules close button itself)isn't going to make Courselab trigger any events.
Moodle itself is supplying the environment the module runs in.
It sounds like this is something that Moodle is doing.
Have you checked the fora for this, I remember reading that there were a mixed bag of issues with scorm that had been introduced, I suspect most are resolved but this might need a newer subversion or patches.
Nick :)
Hi Pamela,
All of the completion variables or vatiables you set in a module are empty until used or updated. Some do update on closure but the trigger is within Courselab. That is something in the module triggers it, it isn't externally triggered by in this case closing the browser window.
Closing using the exit button of a browser (rather than the modules close button itself)isn't going to make Courselab trigger any events.
Moodle itself is supplying the environment the module runs in.
It sounds like this is something that Moodle is doing.
Have you checked the fora for this, I remember reading that there were a mixed bag of issues with scorm that had been introduced, I suspect most are resolved but this might need a newer subversion or patches.
Nick :)
