Closed jstuckle closed 12 years ago
Changes elsewhere in the code exposed this problem.
The SCOs are actually marked as completed - but the LMSInitialize call kept resetting the current SCO back to the first one.
This was because the SCO id was hard coded in the LMSInitialize call, instead of using the global variable glbSCOID. It didn't cause a problem before because that was the only place it was used. However, when we changed the code to more correctly track the SCO status, the hard-coded value was used other places, also.
I changed the code to use the glbSCOID, which correctly tracks the currently executing SCO and SCO processing works fine now.
SCO's are not being marked as completed when they should be.