It will take about one month to implement converting word fields to pdf fields, because of some tech issues that Aspose.Word team is now figuring out .
Currently we don’t have such support for dynamic creation of Formfield in Aspose.Pdf.Kit, maybe we should take it into account in future development plan.
I am a program manager for Merrill Lynch, and we recently purchased Aspose Word.
I am interested in the ability to add a button to an already We can currently use the fileMend feature to draw the image into the document, but we want to have the ability to remove that image if we desire. One way I can think of to do this is to add a button to an already existing PDF document. Then set an image on that button.
I am a program manager for Merrill Lynch, and we recently purchased Aspose Word.
I am interested in the ability to add a button to an already We can currently use the fileMend feature to draw the image into the document, but we want to have the ability to remove that image if we desire. One way I can think of to do this is to add a button to an already existing PDF document. Then set an image on that button.
As what ken has replied, Kit can paste an image to an existing button field. But the function of add/delete a button field into PDF template will be availabe in the next version before this weekend. BTW, would you mind if the API need the exact coordinates (llx, lly, urx, ury) as parameter? We will very appreciate your advice.
We would also like to see a way to create form fields from the
Aspose.Pdf.Kit component. The Form class has GetField(),
MoveField() and FillField() methods but no CreateField() method.
I think a CopyField() method and a CopyFieldGroup() method would also
be extremely useful. Let’s say I create 5 fields that I can
select as a group. If I want to copy those 5 fields X times, I’d
need a convenient method for doing so.
We DO appreciate your instructive advice very much. It is coincident that we have seriously considered all the interfaces you mentioned above. In fact, CreateField() and CopyField() have been implemented, while CopyFieldGroup() is under developing. They will be all published in the next version soon (but not the same names :).
CreateField() and CopyField() can be surely released in the new version Kit 2.1 within this month. After a week, CopyFieldGroup() will be also released.