[MeeGo-touch-dev] MeeGo Touch style/objectName changes
peter.csaszar at blumsoft.eu
Wed Sep 15 03:26:48 PDT 2010
For having spacer widgets with the style CommonSpacer, I had to use MWidgetController instead of MWidget. Now I get a
lot of such messages on terminal:
Could not find view class for: MWidgetController / "default"
What should I do to not have these messages without having to define view classes?
On 08/31/2010 12:35 PM, Tomas Junnonen wrote:
> As of MeeGo Touch 0.20.37 there is a new way of binding styles from the
> theme to widgets.
> Previously we overloaded the meaning of Qt's existing setObjectName
> method to influence the style selection, but this turned out to be a bit
> problematic in some cases; as an example, automatic testing suites may
> want to use Qt's objectName to uniquely identify a component while a
> style name on the other hand may be applied to multiple components.
> So, now we have a new API just for specifying the style in apps:
> - MWidgetController::setStyleName
> We recommend using this form from now on, as well as converting existing
> use of setObjectName to setStyleName. Code that currently uses
> setObjectName for styling will however continue to work as before (if
> styleName is undefined the objectName is used), but we are deprecating
> the setObjectName overload so in the future this may no longer be
> MeeGo-touch-dev mailing list
> MeeGo-touch-dev at meego.com
More information about the MeeGo-touch-dev