PDF Viewer widget: expected experience from set the currentDestination?
keith.clarke at me.com
Thu Dec 23 04:13:06 EST 2021
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?
> On 23 Dec 2021, at 03:53, Monte Goulding via use-livecode <use-livecode at lists.runrev.com> wrote:
> Hi Keith
> Yes it does look like the currentDestination docs leaves a lot to be desired. I think there’s a couple of missing related items which is making the document display incorrectly. I’ve created an issue for that here https://quality.livecode.com/show_bug.cgi?id=23493
> Here’s a simple example of using the currentDestination though:
> local tDest
> put "goto" into tDest["type”]
> put "Fit" into tDest["mode”]
> put 3 into tDest["page”]
> set the currentDestination of widget “pdf" to tDest
>> On 23 Dec 2021, at 4:24 am, Keith Clarke via use-livecode <use-livecode at lists.runrev.com> wrote:
>> Hi folks,
>> Please can anyone share the response/experience to be expected in the PDF Viewer widget after a successful call to set the currentDestination?
>> I have the widget successfully changing currentPage when set but I was hoping to see some visual feedback with on a change of currentDestination - to perhaps highlight something or zoom or scroll the named destination into focus?
>> Unfortunately, the dictionary entry for currentDestination doesn’t help as it has no examples and the description of as it seems to be missing chunks of critical text regarding the ‘receive’ end of the message...
>> "This is the format that is sent as a parameter in the message and is used by the <????> and <????> and properties for goto type destinations:...”
>> Perhaps I’ve missed some settings on the widget to allow it to respond to this message?
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode