Degrafa States Memory Management

Question

I was recently profiling my application that uses Degrafa States in the skins and noticed that doing so uses more memory than I expected. Between the SetProperty and State, they were using about 10% of the total used application memory.

Would it be better to use css for the state changes and a new skin for each state?

or

Are there some simple tips to reducing the memory footprint of degrafa?

Answer 1

States in Degrafa skins aren't exactly like they are for UIComponents. For starters they're selected by the "name" property, rather than "currentState". Besides that, it's out of your control, the UIComponent that you're skinning will always create a new skin instance for each state, unless you've set xxxSkin:ClassReference(null); in your CSS. Degrafa States just allow you to write a more readable and maintainable skin class that can be instantiated for each "state" of the skinned UIComponent.