[build 390] GoToR action "Go to a Page in Another Document" to a named destination does not work at all SOLVED

[rakunavi]

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

Hello all,

In build 390, when "Go to a Page in Another Document" is specified as the action for a bookmark or link and a named destination is specified, I found that the action does not work at all. Also, even if you try to specify a named destination by specifying a new action, it appears that the setting was not reflected at first glance.

The following is a verification procedure.

1. Open Doc_A.pdf in build 389 and click on the bookmark "GoToR DocB-Page_77".
2. The destination "GoToR DocB-Page_77" of Doc_B.pdf corresponding to "GoToR DocB-Page_77" will open.
3. Open the bookmark properties of Doc_A.pdf and make sure the destination is set to "GoToR DocB-Page_77" for Doc_B.pdf.
   All operations up to this point are normal.
4. Open Doc_A.pdf in build 390 and click on the bookmark "GoToR DocB-Page_77".
5. Doc_B.pdf opens, but only the first page is displayed, not the page specified by the bookmark.
6. Open the bookmark properties of Doc_A.pdf and see that Doc_B.pdf is only shown as the destination, and the destination is blank.
7. Create a new bookmark in Doc_A.pdf, create "GoToR DocB-Page_99" and set the destination to "GoToR DocB-Page_99", the destination of Doc_B.pdf.
8. After setting the destination, reopen the Action List dialog and confirm that the destination is blank and does not seem to reflect the setting.
9. Save Doc_A.pdf as test.pdf.
   Verification of Step 4 through Step 8 shows that the GoToR action for named destinations in build 390 does not work at all, and the settings are not reflected correctly in the dialog when creating a new action.
10. Open test.pdf in build 389 and click on the bookmark "GoToR DocB-Page_99".
11. The page corresponding to the named destination "GoToR DocB-Page_99" in Doc_B.pdf, which was specified in the bookmaark "GoToR DocB-Page_99" in DocA.pdf, opens.
    
    As shown in Step 10 and Step 11, the GoToR link for named destination created in build 390 will work in build 389.

• Animation.gif

• SampleFiles.zip

This is a very serious issue for users of named destinations. It appears that multiple issues have occurred since build 388, probably as a result of the changes made in this topic. I strongly recommend that users of named destinations revert to build 387.

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

Best regards,
rakunavi

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

[Ivan - Tracker Software]

We will release build 391 with the fix.

[rakunavi]

Hello Ivan, thank you for taking the time to let us know.

Related to this issue, I have found that when exporting and importing links from the options menu of the Links pane in build 390, the destination of the link in the GoToR action that is destined to a named destination will not work.

Below are the results of the same procedure verified on build 387 and build 390 for the two documents that are mutually linked to each other.

The verification procedure is as follows

1. Open sample_A.pdf and sample_B.pdf and check if the GoTo/GoToR action links on each page work.
2. Open the Links pane of sample_A.pdf and export all links in XFDF format.
3. Delete all links in the Links pane, then import the exported file to restore the links.
4. Save the file in a folder with the same name as the build number using the "Save As" command.
5. For sample_B.pdf, follow the same procedure as in Step 2 through Step 4.
6. After importing the links, check the sample_A.pdf and sample_B.pdf to see if the GoTo/GoToR action links work on each page.

The root directory of the attachment contains the original two sample documents. The folders for each build number contain the files after exporting and importing the links, as well as the exported XFDF files.

• SampleFiles.zip

• Animation.gif

As you can see in the video, the GoToR action links work in build 387, but in build 390, the file opens but does not go to the target page.

For reference, here is an extract of the relevant parts of the sample_A.xfdf export file for build 387 and build 390.

• build 387 - Page 1
  <GoTo><Dest><Named Name="A_Page_1"/></Dest></GoTo>
  <GoTo><Dest><Named Name="A_Page_2"/></Dest></GoTo>
  <GoTo><Dest><Named Name="A_Page_3"/></Dest></GoTo>
  <GoTo><Dest><Named Name="A_Page_4"/></Dest></GoTo>
  <GoTo><Dest><Named Name="A_Page_5"/></Dest></GoTo>
  <GoToR><File OriginalName="./sample_B.pdf"/><Dest><Named Name="B_Page_1"/></Dest></GoToR>
  <GoToR><File OriginalName="./sample_B.pdf"/><Dest><Named Name="B_Page_2"/></Dest></GoToR>
  <GoToR><File OriginalName="./sample_B.pdf"/><Dest><Named Name="B_Page_3"/></Dest></GoToR>
  <GoToR><File OriginalName="./sample_B.pdf"/><Dest><Named Name="B_Page_4"/></Dest></GoToR>
  <GoToR><File OriginalName="./sample_B.pdf"/><Dest><Named Name="B_Page_5"/></Dest></GoToR>
  
  build 390 - Page 1
  <GoTo><Dest><Named Name="A_Page_1"/></Dest></GoTo>
  <GoTo><Dest><Named Name="A_Page_2"/></Dest></GoTo>
  <GoTo><Dest><Named Name="A_Page_3"/></Dest></GoTo>
  <GoTo><Dest><Named Name="A_Page_4"/></Dest></GoTo>
  <GoTo><Dest><Named Name="A_Page_5"/></Dest></GoTo>
  <GoToR><File OriginalName="./sample_B.pdf"/><Dest><XYZ Page="4294967295"/></Dest></GoToR>
  <GoToR><File OriginalName="./sample_B.pdf"/><Dest><XYZ Page="4294967295"/></Dest></GoToR>
  <GoToR><File OriginalName="./sample_B.pdf"/><Dest><XYZ Page="4294967295"/></Dest></GoToR>
  <GoToR><File OriginalName="./sample_B.pdf"/><Dest><XYZ Page="4294967295"/></Dest></GoToR>
  <GoToR><File OriginalName="./sample_B.pdf"/><Dest><XYZ Page="4294967295"/></Dest></GoToR>
  

In build 390, you can see that the part indicated by red letters is completely abnormal.

Regarding the bookmark export and import functionality, as discussed in a separate topic here, since build 388, the GoToR action with a named destination is now changed to a page number. This is a very troubling change for me, but for bookmarks, I can still get around the problem by exporting and importing the bookmark as a text file and keeping the named destinations.

However, there is no such workaround for exporting and importing links. If this is not due to just a bug, but is intended to change the GoToR actions from named destinations to page numbers, as well as bookmarks, and that is a decision that will not be overturned, then the last build of PDF-XChange Editor for me would be build 387.

Of all the problems I have reported over the past three years, this one is the most serious, surpassing the problem of garbled Japanese comments. If you don't realize the severity of this problem, it is because you are not making the most of named destinations.

I hope that there will be more understanding and love for named destinations.

Best regards,
rakunavi

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

[Daniel - PDF-XChange]

Hello, rakunavi

Thank you for the information, I have forwarded this to Ivan once again for another review. I know build 390 had a number of issues relating to Named destinations which we are working on, hopefully this is included in that list, but if it is not already, it will be on his radar soon.

Kind regards,