A/V error using IsAnnotFormField

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

I just received this report from one of my developers using QuickPDF Library 8 in our Delphi 7 project:

"As I mentioned on the phone, QuickPDF (QPDF) identifies form fields as annotations, specifically as Widgets. There is a function called IsAnnotFormField which tells us if the "annotation" is actually a form field. When I first tried IsAnnotFormField, I got an Access Violation whenever I checked a form field. Turns out the access violation appeared because QPDF's internal field list had not been initialized."

My guy was trying to directly access a field that was known to exist on the form. The only way he saw to get around the error was to first call FormFieldCount which seems to initialize the internal data structure representing form fields; without this call, the list that references the form fields doesn't appear to get initialized. Shouldn't QuickPDF initialize its internal lists without the need for us to call this method? Or is there something we missed?

Thank you.
Rich

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
rackerson Members Profile Find Members Posts Beginner Joined: 27 Oct 11 Location: New Jersey Status: Offline Points: 5	Post Options Post Reply Quote rackerson Report Post Thanks(0) Quote Reply Topic: A/V error using IsAnnotFormField Posted: 27 Oct 11 at 6:41PM
	I just received this report from one of my developers using QuickPDF Library 8 in our Delphi 7 project: "As I mentioned on the phone, QuickPDF (QPDF) identifies form fields as annotations, specifically as Widgets. There is a function called IsAnnotFormField which tells us if the "annotation" is actually a form field. When I first tried IsAnnotFormField, I got an Access Violation whenever I checked a form field. Turns out the access violation appeared because QPDF's internal field list had not been initialized." My guy was trying to directly access a field that was known to exist on the form. The only way he saw to get around the error was to first call FormFieldCount which seems to initialize the internal data structure representing form fields; without this call, the list that references the form fields doesn't appear to get initialized. Shouldn't QuickPDF initialize its internal lists without the need for us to call this method? Or is there something we missed? Thank you. Rich

Ingo Members Profile Find Members Posts Moderator Group Joined: 29 Oct 05 Status: Offline Points: 3524	Post Options Post Reply Quote Ingo Report Post Thanks(0) Quote Reply Posted: 27 Oct 11 at 10:55PM
	Hi Rich! This here is a user-user-forum. If you miss functionalities you should post it on the official support pages. My opinion: Yes you're right but in real life this doesn't matter 'cause you're using FormFieldCount first to check if there are formfields? Cheers, Ingo

rackerson Members Profile Find Members Posts Beginner Joined: 27 Oct 11 Location: New Jersey Status: Offline Points: 5	Post Options Post Reply Quote rackerson Report Post Thanks(0) Quote Reply Posted: 27 Oct 11 at 11:20PM
	Thanks for the reply. I didn't realize this wasn't the official support pages or I would have posted to them instead. You are correct. In real life our code would check if there were form fields first before attempting to access them. Nevertheless I will contact support about a better way to initialize fields.

AndrewC Members Profile Find Members Posts Moderator Group Joined: 08 Dec 10 Location: Geelong, Aust Status: Offline Points: 841	Post Options Post Reply Quote AndrewC Report Post Thanks(0) Quote Reply Posted: 02 Nov 11 at 7:04AM
	This has been fixed in the 8.13 beta released yesterday. http://www.quickpdflibrary.com/blog/2011/11/quick-pdf-library-8-13-beta-1-released/ Andrew.

rackerson Members Profile Find Members Posts Beginner Joined: 27 Oct 11 Location: New Jersey Status: Offline Points: 5	Post Options Post Reply Quote rackerson Report Post Thanks(0) Quote Reply Posted: 02 Nov 11 at 1:25PM
	Thanks for being so responsive! I will download the beta now to test.