Revision history [back]

I recently realised that new methods have been added to the OpenNI API to allow saving/loading skeleton calibration data to a file. However, I've trying to make them work without success. The methods I'm talking about are

XnStatus xn::SkeletonCapability::SaveCalibrationDataToFile(XnUserID user, const XnChar * strFileName)
XnStatus xn::SkeletonCapability::LoadCalibrationDataFromFile(XnUserID user, const XnChar * strFileName)

Has anyone managed to use those successfully?

I recently realised that new methods have been added to the OpenNI API to allow saving/loading skeleton calibration data to a file. However, I've trying to make them work without success. The methods I'm talking about are

XnStatus xn::SkeletonCapability::SaveCalibrationDataToFile(XnUserID user, const XnChar * strFileName)
XnStatus xn::SkeletonCapability::LoadCalibrationDataFromFile(XnUserID user, const XnChar * strFileName)

Has anyone managed to use those successfully?

I recently realised that new methods have been added to the OpenNI API to allow saving/loading skeleton calibration data to a file. However, I've trying to make them work without success. The methods I'm talking about are

XnStatus xn::SkeletonCapability::SaveCalibrationDataToFile(XnUserID user, const XnChar * strFileName)
XnStatus xn::SkeletonCapability::LoadCalibrationDataFromFile(XnUserID user, const XnChar * strFileName)

Has anyone managed to use those successfully?

Update: The code I used to test this is a modified version of openni_tracker.cpp in trunk. You can check lines 201 to 268 in http://pastebin.com/d0m6J6tb

The service requests contain the user id (int) and a filename (string), and I've tried both absolute and relative paths for the filename without success.