Did some more research. Yup - the image renders in the canvas asynchronously. So, on first load it is exporting the canvas image before that image is rendered.
Going to see if I can add an event handler that is triggered when the canvas is finished. Thanks for the tip :) Sent from my iPhone > On May 11, 2017, at 5:59 PM, jonathandly...@gmail.com wrote: > > Ah > > Yes - the svg data is cached. > > That would explain why it must happen for every image. > > Thanks Hermann. > > I will tinker some more. > > Sent from my iPhone > > On May 11, 2017, at 5:52 PM, hh via use-livecode > <use-livecode@lists.runrev.com> wrote: > >>> JL wrote: >>> If it were from that, then we could not switch back and forth >>> between resizing different images. It would show the output of >>> the previous image processed. But that does not happen. >>> I thought I chained the commands linearly, but I will check >>> that again. >> >> I didn't say the second call shows the result from the _previous_ call, >> I said it shows the result from the meanwhile finished _first_ call >> (with that svg data, that is thereafter cached). >> >> >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
