So, as I see things, there are two ways to do custom styles in a custom component. The first is the quick and easy way: create a public Bindable of type uint and then use data binding inside your custom component. Your component then has properties for the styles. The second is the more long winded approach of adding meta data, and writing all the code needed to support that. Your component then has actual styles that can be set using setStyle(), but from MXML looks exactly the same as the first way.
Given we don't use setStyle(), and use custom components mostly from MXML (rather than AS), is it very wrong to just do it the first, esp. if there are many styles ? -- Tom Chiverton **************************************************** This email is sent for and on behalf of Halliwells LLP. Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at Halliwells LLP, 3 Hardman Square, Spinningfields, Manchester, M3 3EB. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by The Solicitors Regulation Authority. CONFIDENTIALITY This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 2500. For more information about Halliwells LLP visit www.halliwells.com.
