On 05/05/2010, at 4:40 PM, ext Alexis Menard wrote: * Event handling is problematic as there is no pass through. If an Element does not handle an event there is no way to pass the event to its parent.
Note that mouse events are accepted by default, so in a MouseArea you need to explicitly set mouse.accepted to false in order for the event to propagate (and also in the case of mouse events, they are not sent to the parent but to the next mouse handler visually 'behind' the current one) * Lack of a size hint is also a problem. Any specifics? What is trying to be accomplished, and how is the lack of size hints preventing it? * Lack of font metrics makes working with text difficult. If the size is defined in the parent, can't figure out how big the text is to resize the parent to it. For example, rotate a Text element 32 degrees and put it into a unrotated rect of just the right size. Size hint would help here. Does http://bugreports.qt.nokia.com/browse/QTBUG-9712 cover the issues here? * More drawing primitives such as rounded polygons would be useful. Trying to design as edge with a rounded flap on the side for dragging is not easy. Performance of applications built with out-of-the-box QML is very important to us, and the initial set of primitives was chosen (in part) as a set of things that we felt we would guarantee reasonable performance. Two implementation choices for other drawing primitives at the moment are: * create a custom element in C++ via subclassing QDeclarativeItem (or QGraphicsWidget) * create an image in an image editor and use Image or BorderImage from QML to load it Regards, Michael
_______________________________________________ Qt-qml mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-qml
