| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | fix tests for QT_NO_PROCESS and when running tests as root | Harald Fernengel | 2009-07-21 | 1 | -0/+4 |
| | | |||||
| * | Merge license header changes from 4.5 | Volker Hilsheimer | 2009-06-16 | 3 | -6/+6 |
| |\ | |||||
| | * | Update license headers as requested by the marketing department. | Jason McDonald | 2009-06-16 | 3 | -6/+6 |
| | | | | | | | | | Reviewed-by: Trust Me | ||||
| * | | handle qreal properties correctly in the meta-object system | Kent Hansen | 2009-06-05 | 1 | -0/+27 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When cross-compiling, it's possible that the size of qreal for moc itself (host platform) is different from the size of qreal on the target platform. Thus, we should not encode the metatype-id of qreal at moc time. Instead, use QMetaType::QReal in the generated code so that the the property flags are only derived at compile time. We also need to support the pesky QT_COORD_TYPE. In this case, qreal can be _any_ type (not just float or double), so we encode the property type as 0 and have a special check in QMetaProperty::type() that resolves the correct type at runtime. Reviewed-by: Simon Hausmann | ||||
| * | | Add a flag that ensure that a connection is made only one | Olivier Goffart | 2009-05-27 | 1 | -4/+77 |
| |/ | | | | | | | | | | It is often desirable, when doing connection, to ensure that the same connection is only made once. This can be done with the Qt::UniqueConnection 'flag' Also documented the order the slot are called Reviewed-by: Brad | ||||
| * | Remove obsolete code from autotests. | Jason McDonald | 2009-04-16 | 1 | -6/+0 |
| | | | | | | | | | Each version of Qt has its own set of autotests, therefore preprocessor directives relating to obsolete QT_VERSION's are not necessary. Reviewed-by: Carlos Duclos | ||||
| * | Long live Qt 4.5! | Lars Knoll | 2009-03-23 | 7 | -0/+3085 |
 |
index : Qt.git | |
| Qt s a cross-platform application framework that is used for developing application software that can be run on various software and hardware platforms with little or no change in the underlying codebase, while still being a native application with native capabilities and speed. |
| summaryrefslogtreecommitdiffstats |