|
|
| Line 63: |
Line 63: |
|
| |
|
| ==Required features== | | ==Required features== |
| {|
| |
| |-
| |
| ! Idea:
| |
| ! MouseEvent.globalX/Y
| |
| |-
| |
| | Summary:
| |
| | MouseEvent should also expose globalX and globalY
| |
| |-
| |
| | Proposed solution:
| |
| |-
| |
| | Discussion:
| |
| |-
| |
| |}
| |
|
| |
|
| {| | | {| |
Revision as of 23:24, 9 May 2011
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:
|
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:
|
| Discussion:
|
| Idea:
|
sizeHint
|
| Summary:
|
sizeHint support
|
| Proposed solution:
|
| Discussion:
|
| Idea:
|
Layouts
|
| Summary:
|
Layouts
|
| Proposed solution:
|
| Discussion:
|
