Unintended conversions might occur with the 'Convert to Polyline' feature SOLVED

[rakunavi]

=== UPDATE ===================================================================
The issue reported below has been resolved in Ver 10.4.0 build 388.
I appreciate all the hard work and efforts of the support and development team.
==============================================================================

Hello all,

I found an interesting behavior in 'Convert to Polyline' feature. Specifically, after splitting a rectangular comment into lines using the 'Convert to Lines' feature, delete the top or right edge (See Figure 1). Then select the remaining three edges and apply the 'Convert to Polyline' feature, and the comment will unintentionally revert to a rectangle (See Figure 2). For more information, please see the video.

• Animation.gif
  
  
  before.png
  
  
  after.png

Hoping that the above information will be of some help to you.
Thank you so much for your continued support.

Best regards,
rakunavi

P.S.
Even in build 383, the various buttons on the Help tab, such as Manuals, still access the old domain.

- PDF-XChange Editor Plus Version: 10.1.3 build 383
- OS Version: Windows 11 Home 23H2 Build 22631.2715
- PC Model: Lenovo IdeaPad C340-15IWL, HP All-in-One 22-c0xx

[Stefan - PDF-XChange]

Hello rakunavi,

I reproduced this behaviour however I am not 100% sure if this is bug or it is intended to work this way!
I did create a ticket so that our devs can take a look at that:
#6693: Convert to Polylines makes unexpected shapes
And will let you know as soon as we have any further info.

As for the links - our devs told me that those would be fixed for V10.2 of the Editor.
In the mean time there are redirects in place - so the links will still take you to the desired page!

Kind regards,
Stefan

[rakunavi]

Thank you, Stefan, for creating the ticket and confirming the link.
Best regards
rakunavi

[Daniel - PDF-XChange]

[Stefan - PDF-XChange]

Hello Rakunavi,

Just got an update of the ticket. It is now marked as resolved - so the fix will be included in the next build.

Kind regards,
Stefan

[rakunavi]

Hello Stefan,

Thank you for letting us know. Looking forward to the update.
Please give my best regards to the developers.

Best regards,
rakunavi

[Stefan - PDF-XChange]

[rakunavi]

Hello Stefan,

Just got an update of the ticket. It is now marked as resolved - so the fix will be included in the next build.

Stefan informed me the other day that "It is now marked as resolved", but I have tested with build 387 released today and the issue continues to exist. I tried the same verification scenario as in the initial report, and the behavior is exactly the same. It is possible that the issue was marked as "resolved" in Tracker's incident management database due to confusion with other issues. Personally, I do not think that this case is of high importance. I dare say it is low. However, I am concerned that it may be removed from Tracker's incident handling flow, so I am just letting you know.

Best regards,
rakunavi

P.S.
The issue that Japanese users, including myself, are waiting for a long time is the garbled Japanese comment issue, which was expected by Vasyl to be almost 100% fixed in build 386. The issue continues in build 387. I sincerely hope that the issue will be fixed in build 388. I believe in "third time's the charm". Until this issue is resolved, I cannot confidently recommend that Japanese Acrobat users switch to PDF-XChange Editor.

[Stefan - PDF-XChange]

Hello rakunavi,

Thanks for testing this, and sorry to hear that it is still an issue in 387 for you! I've reopened the ticket and asked my colleagues to investigate this once again!

Kind regards,
Stefan