Hello all, I've collected those feedback :
* Mouse selection needs to be implemented in each list view with a mouse area. It is necessary to implement the logic of "when an item is clicked, make it the current item", whereas keyboard selection is built in. * Can't access the data of the current item in the view from outside the delegate. Inside the implementation of a delegate, it is possible to use model.customDataRole inside the implementation of a delegate, but if in another element you want to get particular data for "the current item selected in that view", it doesn't seem possible in QML. * 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. * Lack of widgets for basic elements such as Buttons, sliders scrollbars leads means they all have to be implemented from scratch visually and logically, perhaps badly. * Lack of a size hint is also a problem. * Should there be a hook for when new children are added to an Element? onChildrenChanged is not (currently?) working as expected. * 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. * 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. * Images can be used but must be hardcoded for one dpi. Any comments? _______________________________________________ Qt-qml mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-qml
