Thanks Slav. This info may save me from wasting my time "guessing" how to modify the SCORM_SaveInteractions() function.
An alternative approach/solution I have been looking at is minimizing the amount of data stored into cmi.suspend_data.
The only data I need stored in cmi.suspend_data is the ID and LearnerResponse. So far, I have been able to prevent the following data from being saved in cmi.suspend_data: Type, Weighting, Timestamp, Latency, and Result.
There are two additional pieces of data that I want to prevent saving to cmi.suspend_data, namely the Description and something that looks like: < r r > < r p = \ " 0 \ " / > < / r r >
(just remove the spaces expect the one between the r and the p)
Do you know how this can be done?
Thanks!
-Dan
By the way, I've posted this question with more details elsewhere in this community, the title of the post is "SCORM 1.2 and cmi.suspend_data element size limit"
Thanks Slav. This info may save me from wasting my time "guessing" how to modify the SCORM_SaveInteractions() function.
An alternative approach/solution I have been looking at is minimizing the amount of data stored into cmi.suspend_data.
The only data I need stored in cmi.suspend_data is the ID and LearnerResponse. So far, I have been able to prevent the following data from being saved in cmi.suspend_data: Type, Weighting, Timestamp, Latency, and Result.
There are two additional pieces of data that I want to prevent saving to cmi.suspend_data, namely the Description and something that looks like: < r r > < r p = \ " 0 \ " / > < / r r >
(just remove the spaces expect the one between the r and the p)
Do you know how this can be done?
Thanks!
-Dan
By the way, I've posted this question with more details elsewhere in this community, the title of the post is "SCORM 1.2 and cmi.suspend_data element size limit"