PDF Viewer widget: expected experience from set the currentDestination?
monte at appisle.net
Wed Dec 22 22:53:15 EST 2021
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:
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:
More information about the use-livecode