Hi Michael,
we're missing the following line in the qdeclarativeitem.h:
Q_PROPERTY(QGraphicsEffect *effect READ graphicsEffect WRITE
setGraphicsEffect)
As we understand this would be needed to access the property from QML.
When we try to assign the effect anyway our app crashes.
Greetings from Berlin,
Kristian
On 29 Apr 2010, at 08:07 , michael.brasser wrote:
>
> Hi,
>
> Last week I submitted a change that removed the QML bindings for the
> QGraphicsEffects. The reason for this was primarily performance -- although
> we've done several rounds of optimization they still aren't at a point where
> we felt we could give reasonable performance guarantees. We are planning to
> reintroduce effects in a later release, after we've had time to address the
> performance issues.
>
> An example showing how to use a BorderImage for drop shadow effects should be
> showing up in the 4.7 branch soon, and the plan is to add additional examples
> showing how to simulate some common UI effects at low cost using the existing
> QML elements.
>
> 'effect' is still a property of QGraphicsObject, so it is still possible (and
> quite easy) to register and use the effects yourself if necessary:
>
> qmlRegisterType<QGraphicsBlurEffect>("Effects",1,0,"Blur");
> qmlRegisterType<QGraphicsColorizeEffect>("Effects",1,0,"Colorize");
> qmlRegisterType<QGraphicsDropShadowEffect>("Effects",1,0,"DropShadow");
> qmlRegisterType<QGraphicsOpacityEffect>("Effects",1,0,"Opacity");
>
> Regards,
> Michael
_______________________________________________
Qt-qml mailing list
[email protected]
http://lists.trolltech.com/mailman/listinfo/qt-qml
