Windows Mobile Ink APIs are new in Windows Mobile 6 SDK. I guess they are trying to replace the old RichInk APIs.
The way of using Windows Mobile Ink is not complex. The basic idea is to have a IInkOverlay object as an ink collector; an IInkDisp object as a container of strokes data; an IInkStrokes object as a collection of IInkStrokeDisp object. The IInkOverlay object collects the ink data and put them in the IInkDisp object. Then the IInkDisp object put the strokes to the IInkStrokes object.
When the strokes data are in the IInkStrokes object, it's time to get the best recognition result. Currently there are two ways of doing that. One is to directly use the ToString() method to get the best recognition result; the other is to create an IInkRecognitionResult object and use get_RecognitionResult property to get the recognition result set from the IInkStrokes object, then use get_TopString() property to get the best fit result and put it in the BSTR.
/**
* pInkStrokes is the IInkStrokes object.
* pInkRecognitionResult is the IInkRecognitinoResult object.
* StringRecognitionResult is the BSTR.
**/
//Get the best recognition result to the IInkRecognitionResult object
pInkStrokes->get_RecognitionResult(&pInkRecognitionResult);
//Get the best recognition result to the BSTR
pInkRecognitionResult->get_TopString(&StringRecognitionResult);
The first way, using ToString(), seems to be much easier than the second way which is to use IInkRecognitionResult object; However, ToString() is not recommended to be used in this case. I've ever mistakenly used ToString() in this case and had some strange exceptions raised (i.e. WinCE501bException) when my application is not used properly. As the result the correct way of getting ink recognition results is to use IInkRecognitionResult object and its properties.