This is actually another issue with the inheriting style approach I had
originally proposed - it requires each ancestor to maintain the set of declared
styles so that descendants can inherit them. In many (if not most) cases, the
only time an application will need these styles is when the UI is
>> Again, I'm not sure how often this might be used in a real application,
>> but it could be supported easily.
> Me too, but if it's "easy" to implement why not ?
Because there are other issues, like the fact that listening for style changes
on these objects would require keeping them in memory
27;d keep autoUpdate by default false (safer).
Bye,
Sandro
--
View this message in context:
http://apache-pivot-developers.417237.n3.nabble.com/Auto-updating-styles-tp942381p943925.html
Sent from the Apache Pivot - Developers mailing list archive at Nabble.com.
It occurred to me earlier that the styling solution I am proposing would
actually support dynamically updated styles. Fundamentally, all styles are set
via Component#getStyles(). This method returns an instance of StyleDictionary
that, in turn, wraps a bean dictionary that wraps the skin. So, a
