Callout Tool becomes TextBox after importing as xfdf

PDF-XChange Viewer SDK for Developer's
(ActiveX and Simple DLL Versions)

Moderators: PDF-XChange Support, Daniel - PDF-XChange, Chris - PDF-XChange, Sean - PDF-XChange, Vasyl - PDF-XChange, Ivan - Tracker Software, Stefan - PDF-XChange

RudolfErnst
User
Posts: 73
Joined: Tue Oct 14, 2008 2:14 pm

Callout Tool becomes TextBox after importing as xfdf

Post by RudolfErnst »

Hello,

the title says it all. We export our comments programmatically as xfdf files (we need xml files). Now we found a problem with the callout tool. After exporting and importing again the type of this comment changes to a text box. This seems to be a bug because exporting a callout comment as fdf file and importing it again leaves the type unchanged.

kind regards
Rudi
User avatar
Stefan - PDF-XChange
Site Admin
Posts: 19885
Joined: Mon Jan 12, 2009 8:07 am

Re: Callout Tool becomes TextBox after importing as xfdf

Post by Stefan - PDF-XChange »

Hello Rudi,

I will pass this for investigation, but could you please first confirm the SDK build you are using, as if it is not the latest this might have already been fixed.

Best,
Stefan
RudolfErnst
User
Posts: 73
Joined: Tue Oct 14, 2008 2:14 pm

Re: Callout Tool becomes TextBox after importing as xfdf

Post by RudolfErnst »

Hello Stefan,

we are using the ActiveX-Control of Pdf-XChange 2.0 Build 55.0

kind regards
Rudi
User avatar
Stefan - PDF-XChange
Site Admin
Posts: 19885
Joined: Mon Jan 12, 2009 8:07 am

Re: Callout Tool becomes TextBox after importing as xfdf

Post by Stefan - PDF-XChange »

Hello Rudi,

I have created a ticket in our internal system #479 so that our developers can schedule it for fixing.
We will notify you as soon as we have any news.

Best,
Stefan
User avatar
Stefan - PDF-XChange
Site Admin
Posts: 19885
Joined: Mon Jan 12, 2009 8:07 am

Re: Callout Tool becomes TextBox after importing as xfdf

Post by Stefan - PDF-XChange »

Hello Again Rudi,

Just got a confirmation from our dev team that this trouble would be fixed in the next build of our Viewer (2.5) which is a few weeks away.

Regards,
Stefan
User avatar
Ivan - Tracker Software
Site Admin
Posts: 3586
Joined: Thu Jul 08, 2004 10:36 pm

Re: Callout Tool becomes TextBox after importing as xfdf

Post by Ivan - Tracker Software »

Fixed (P.S. Never trust Adobe's specification! )
PDF-XChange Co Ltd. (Project Director)

When attaching files to any message - please ensure they are archived and posted as a .ZIP, .RAR or .7z format - or they will not be posted - thanks.
RudolfErnst
User
Posts: 73
Joined: Tue Oct 14, 2008 2:14 pm

Re: Callout Tool becomes TextBox after importing as xfdf

Post by RudolfErnst »

Hello Ivan,

thank you for the bug fix , I verified it and found out that the comment type is left unchanged now. This is ok, the apperance/properties of the comment however are still changed. In my case the stroke color changes from red lines to black lines and the line ending style changes from "open arrow" to "none". This also happens in the standalone viewer not only in the plugin.
Maybe you are loosing this properties during the ExportAnnots call. In some cases PdfXChange writes an <defaultappearance> tag between the <contents-richtext> tag and the </freetext> tag, in most cases however the <defaultappearance> tag is missing.

kind regards
Rudi
User avatar
Stefan - PDF-XChange
Site Admin
Posts: 19885
Joined: Mon Jan 12, 2009 8:07 am

Re: Callout Tool becomes TextBox after importing as xfdf

Post by Stefan - PDF-XChange »

Hello Rudi,

I just spoke with Ivan, and he confirmed that this issue still needs some fixing, so on his request I have made a ticket:
#1072: Issues when importing comments from an xfdf
So that it can be assigned to a developer and resolved.

We will update this topic once there has been some movement on the case.

Best,
Stefan
User avatar
Stefan - PDF-XChange
Site Admin
Posts: 19885
Joined: Mon Jan 12, 2009 8:07 am

Re: Callout Tool becomes TextBox after importing as xfdf

Post by Stefan - PDF-XChange »

Hello Rudi,

I just got an update from our developers that this problem has been fixed and the fix will be in the new build which is expected either tomorrow or on Friday.

Best,
Stefan