Degrafa States Memory Management

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.