PDF Viewer widget: expected experience from set the currentDestination?

[Keith Clarke]

I’m still struggling to find the Rosetta Stone for the PDF widget that connects the page & rect of any currentDestination with its link text on that page of the PDF, to enable recreation with scripting of the links that one sees out-of-the-box in PDF viewers such as Preview or Adobe.

I must have missed something as it would appear that the metadata peters out after one has established that a page ’n’ in the PDF document contains:
- via currentDestinations: none to maybe a few dozen links, each with part of an ‘href’ and it’s rect top-left corner defined, but no label text or page text start & end offsets;
- via hilitedRangeText: a chunk of plain text with no html or other ‘markup’ hints at what might constitute link text;
- ...and never the twain shall meet. 

If this is really the state of the art with the widget and its wrapping of PDFium, I can’t see how it can be scripted to work - so I think I’ll need to start looking elsewhere, outside of LC for a mechanism to access PDF text & links.

Please tell me I’m wrong and am missing something obvious?
Best,
Keith
 
> On 23 Dec 2021, at 09:13, Keith Clarke via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Thanks Monte - that code sorts the *calling* end of the recipe and the widget changes page to the one containing the currentDestination.
> 
> However, what about the *receiving* end of the recipe? Nothing seems to be happening upon arrival at the page to get any closer to this particular destination amongst the many on the same page. 
> 
> Where should one look to understand the options and handlers for the specific destination upon arrival *after* the change of page, re scroll into view, zoom, focus, setting the associated hilited text, etc?
> Best,
> Keith 
>