Hello Mohammed,
You said ""while capturing the PDF Object properties using ""Surface automation region mode"". This gives me a hint about the way you are working with this document..
Adobe describe the following ways in which Windows applications can interact with their product's documentation objetc model (DOM):
""● On the Microsoft® Windows® operating system, Acrobat and Adobe Reader export PDF content as COM
objects. Accessibility applications such as screen readers can interface with Acrobat or Adobe Reader in
two ways:
● Through the Microsoft Active Accessibility (MSAA) interface, using MSAA objects that Acrobat or
Adobe Reader exports
● Directly through exported COM objects that allow access to the PDF document’s internal structure,
called the document object model (DOM).
The DOM and MSAA models are related, and developers can use either or both. Acrobat issues
notifications to accessibility clients about interesting events occurring in the PDF file window and
responds to requests from such clients.""
This is from the document ""PDF Accessibility API Reference"" which is available here:
http://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pdfs/access.pdf
When you are using the Region Mode you are only comparing a picture ""we call it a ""region"") with another picture (e.g. a picture of some part of your PDF document). You are not interfacing with the PDF document's object model in that spy mode. That is why the error is reporting ""The window spied was not found in the model"".
To interact with the PDF's DOM I suspect you will need to access it using a spy mode such as Active Accessibility.
With regards,
Chris.
