brian at milby7.com
Wed Feb 6 22:20:09 EST 2019
I don’t think that leak is browser widget specific. I was able to reproduce the effect of increasing memory usage with the tree view widget, but much more slowly.
On Feb 6, 2019, 9:22 PM -0500, hh via use-livecode <use-livecode at lists.runrev.com>, wrote:
> > BR wrote:
> > Now, if I could only figure out how to use a series of images
> > instead of just two?
> You can set new images at any time, even during rotation. Setting
> an image needs at about 10 millisecs (the widget has to adjust its
> size). See the help at topright of the sample stack.
> The video grabbing is not optimized. I could better grab the frame
> But I used a snapshot from the rectangle of the widget because
> = the browser widget is still memory leaking when using JS
> = the snapshot is a better example for people who don't know JS.
> Disadvantage: On some hardware a bit "jerkiness".
> 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