I'm looking at optimizing my code as much as possible using greensock v11 (+ starling and feathers) and Adobe Scout.
I could identify the broadcast of many "progress" events as a place that takes quite a bit my iphone 4 cpu time.
Since I do not add any callback to onProgress, I did expect the library to not broadcast those events.
But after looking at the source code, it seems that, as I use a GroupLoader with subloaders (because I load textures atlases with .png + .xml at the same time), the GroupLoader will register listener for those events on it's childs anyway.
Mobile performance - Avoid PROGRESS events
in Loading (Flash)
Posted
Hi,
I'm looking at optimizing my code as much as possible using greensock v11 (+ starling and feathers) and Adobe Scout.
I could identify the broadcast of many "progress" events as a place that takes quite a bit my iphone 4 cpu time.
Since I do not add any callback to onProgress, I did expect the library to not broadcast those events.
But after looking at the source code, it seems that, as I use a GroupLoader with subloaders (because I load textures atlases with .png + .xml at the same time), the GroupLoader will register listener for those events on it's childs anyway.
Is there something I can do ?
Thanks,
Sebastien