Memory Management with CocoonJS

Hello,

We have a new plugin update. Please, have a look at it, because we fixed an important issue regarding the Webview+.

https://github.com/ludei/Construct-2-plugin

There was a problem with the screencanvas when using it on non canvas+ environments (as the new Webview+).

It should work fine now.

Regards.

Hello,

We have a new plugin update. Please, have a look at it, because we fixed an important issue regarding the Webview+.

https://github.com/ludei/Construct-2-plugin

There was a problem with the screencanvas when using it on non canvas+ environments (as the new Webview+).

It should work fine now.

Regards.

then your new plugin about memory management is only supported for ios8 ?

Hello,

> Hello,

>

> We have a new plugin update. Please, have a look at it, because we fixed an important issue regarding the Webview+.

> https://github.com/ludei/Construct-2-plugin

> There was a problem with the screencanvas when using it on non canvas+ environments (as the new Webview+).

> It should work fine now.

>

> Regards.

>

then your new plugin about memory management is only supported for ios8 ?

No, not at all. We fixed a bug regarding non-canvas environments, as the new Webview+. But that doesn't mean it is not available for the rest of the iOS versions or Android.

If you use the latest plugin + 2.1 version of the launcher or the cloud, you will have the Lazy loading by default and the rest of the new options we added recently. If you compile your project in the 2.0.2, even if you use the new plugin, you won't have lazy loading. The third option available if you wan't to use the 2.1 but you don't like the lazy loading is editing the files after compilation to disable the lazy loading on the project. It can't be done in other way, sorry.

Regards.

Just wondering, the methods "image.dispose image.dispose && ();" not yet been added to construct right? Using only the lazy loading, switching between layouts is too slow, with many loadings.

I like how the performance improved with this new approach, but do not want to go back to the old method just to get rid of these loadings.

Some light at the end of the tunnel ludei? Any news that can help with this part? XD

Yeah, to make the layout by layout loading to be usable, we need a way to show a loading bar between layouts.

Hello,

I can explain you how to disable the lazy loading (as I realized it is changed in the r187), but it is not in our hand to enable the loading screen between layouts, sorry.

Regards.