Hi Sebastian, > The problem is that we need to support multiple values for each > properties. Then we could add some fallback logic to do something like > user-value -> appearance-value -> default-value -> null
Yes, that would solve the problem. Then, manually set properties would always supersede any appearance settings. On the other hand, mouse over effects would not work anymore when user values are set. To maintain them, a derived class would have to define a new Property (e.g. hoverColor). > Hope this helps. Indeed, it's fine to know that the problem will be solved. Thanks, Ralf ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
