| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
QDeclarativeXXX.
|
|
|
|
|
|
|
|
| |
As a value type QmlListProperty doesn't consume any memory in the object.
It also has a companion QmlListReference class that is part of the public
API for C++ developers to interact with that also manages memory issues
that existed with previous solutions (if the containing QObject was
destroyed it left a dangling pointer).
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
| |
This reverts commit d914555badcd4761864657e1e335e657b791453f.
|
| |
|
|
|
|
| |
QTBUG-5675
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This should allow QGuard to be removed from Qt and QObjectPrivate::ExtraData.
Having QmlGuard inside QmlDeclarativeData reduces the number of new's, and
creating QmlDeclarativeData is faster than QObjectPrivate::ExtraData anyway.
|
|
|
|
|
|
|
|
|
|
|
|
| |
- include headers from own directory with ""
- include headers from own project without private/
- sort includes from most specific to most generic
- make headers self-contained
- some whitespace unification
no attempt was made at making the qt includes consistent regarding the
use of module names and forwarding headers.
no attempt was made at sorting includes.
|
|
|
|
| |
It seems we're going to have to so a syncqt/configure in Qt modules.
|
|
|
|
| |
May help modularization (syncqt and configure are Qt-specific).
|
| |
|
| |
|
|
Eventually this should be extended to support modifying list properties.
|