Rick, On Thu, May 28, 2009 at 9:54 AM, Rick Winscot <[email protected]>wrote:
> Your observation that your application footprint increased when touching > creationPolicy is what one should expect. > Actually, I wasn't very clear: it wasn't that the application footprint increased (though it did, minimally); rather it was that by having a TabNavigator with a creationPolicy of "all" (which I have now managed to work around), five components were created immediately, each of which added to the CPU load because of the skinning issue that was common to all of them. an increased footprint when adding skins into the mix is also something you > will probably see. > Sure. But this is CPU usage caused by the stateful skins. > The part that has me scratching my head is that you are seeing high cpu > usage - which is something that is typically linked to refresh/redraw rates. > Do you have any source we can take a look at? > The source wouldn't help you, Rick. It's very typical forms-in-a-tab navigator stuff. Yes, the issue must be redrawing -- pretty constant redrawing I'd say. If you look at the blog post I referenced, you'll get a better view of the problem. Effective UI did a good deal of testing when they ran into the same issue, and concluded that it had to be a result of the use of stateful skins -- although they didn't seem to be able to determine the underlying cause. They documented some pretty impressive CPU usage by simply adding more skinned elements. I'm just kinda surprised more people haven't run into it. -- Thanks, Tom Tom McNeer MediumCool http://www.mediumcool.com 1735 Johnson Road NE Atlanta, GA 30306 404.589.0560
