This page contains a list of issues and required features that we would like to see fixed/implemented in QML(2)
Enter the issues you wish fixed in the following form:
Issues
| Idea:
|
QtScript integration
|
| Summary:
|
a way to expose from c++ to qml QScriptValues, register non qobject data types and functions
|
| Proposed solution:
|
| Discussion:
|
| Idea:
|
Improved namespace support
|
| Summary:
|
QML should support namespaces in property types (property MyWidgets.Button myProperty)
|
| Proposed solution:
|
| Discussion:
|
| Idea:
|
Improved runtime warnings
|
| Summary:
|
For example: QML should complain when the drag target is invalid
|
| Proposed solution:
|
| Discussion:
|
| Idea:
|
No QtSql dependency
|
| Summary:
|
Remove QtSql dependency from QML library: QtSql should be loadable at runtime
|
| Proposed solution:
|
| Discussion:
|
Required features
| Idea:
|
MouseEvent.globalX/Y
|
| Summary:
|
MouseEvent should also expose globalX and globalY
|
| Proposed solution:
|
adding those properties to the declarative mouse event would be source compatible for existing qml files
|
| Discussion:
|
| Idea:
|
sizeHint
|
| Summary:
|
sizeHint support
|
| Proposed solution:
|
| Discussion:
|
| Idea:
|
Layouts
|
| Summary:
|
Layouts
|
| Proposed solution:
|
current positioners could have an optional property to resize childs that have minimum/maximum/preferredWidth or height not null
|
| Discussion:
|
| Idea:
|
Full set of graphical primitives
|
| Summary:
|
at least Line, Path, Ellipse are missing
|
| Proposed solution:
|
| Discussion:
|
