Previous | Next | (P-PDF) PDF Accessibility

Topic: IPDDomDocument::GetCaret(..) vs the documentation
Conf: (P-PDF) PDF Accessibility, Msg: 145864
From: andreaspetersen
Date: 2/2/2006 12:03 AM

IPDDomDocument::GetCaret(..) doesn't act as it is supposed to according to the documentation (https://partners.adobe.com/public/developer/en/pdf/access.pdf). At least as I read the documentation.

In the description of the function it says that "The node may be a word or a form field". But my experiments with this function shows that sometimes it returns a text node instead of a word node or a form field. The problem is furthermore that the index it also returns doesn't have anything to do with the text node. Instead it shows the index in the word node (that should have been returned).

Do I read the documentation wrong? How are you supposed to understand the word 'may'? I see it as the returned node CAN ONLY be a word node or a form field. But even if it is not only word nodes or text fields, then I guess that the index should match the returned node.

I don't have a bulletproof way of re-creating this problem, but it often happens when I choose the selection-tool (to get a caret), then double-click on a word in the pdf-document to select it and then use IPDDomDocument::GetCaret(..) on the document.

I use Adobe Reader 7.0.5, Microsoft Visual Studio .NET 2003 and C++. I get the Interfaces from the adobe homepage at:
http://partners.adobe.com/public/developer/en/pdf/ClientFiles.zip
linked from this page:
http://partners.adobe.com/public/developer/acrobat/index_advanced.html

Any help is appreciated - thanks