[flame] +1 and http://doc.qt.nokia.com/4.7-snapshot/qml-systempalette.html [/flame]
<http://doc.qt.nokia.com/4.7-snapshot/qml-systempalette.html>I believe that this kind of "style-sheeting" is a bad idea for QML. As I say around the office: "QML requires to have a mind-set change. Much more WebPage and Javascript oriented, then C++ oriented". Something that may also be done is to inject a Style QML object that carries the property that u really need to have "dynamically set". Anyway, there are QML-ways to do what you want, without breaking the Declarative-paradigm. On 13 July 2010 08:10, <[email protected]> wrote: > > [flamebait] > > I have a complete disdain for hardcoding anything in a UI. > > Then you're using the wrong tool. QML is intended to allow designers to do > exactly that. If you want to replicate the 1980s world of UIs generated from > data definitions and infinitely themable but sterile UIs, then you've missed > the QML point entirely. > > -- > Warwick > > _______________________________________________ > Qt-qml mailing list > [email protected] > http://lists.trolltech.com/mailman/listinfo/qt-qml > -- Ivan De Marino | Software Engineer | France Telecom R&D UK - Orange Labs w. +44 20 8849 5806 | m. +44 7515 955 861 | m. +44 7974 156 216 ivan[dot]demarino[at]orange-ftgroup.com | ivan[dot]de[dot]marino[at]gmail[dot]com www.detronizator.org | www.linkedin.com/in/ivandemarino
_______________________________________________ Qt-qml mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-qml
