2011-06-27 14:05:22 +00:00
|
|
|
Some of the changes listed in this file include issue tracking numbers
|
|
|
|
|
corresponding to tasks in the Qt Bug Tracker:
|
|
|
|
|
|
2012-03-02 10:04:01 +00:00
|
|
|
http://bugreports.qt-project.org/
|
2011-06-27 14:05:22 +00:00
|
|
|
|
|
|
|
|
Each of these identifiers can be entered in the bug tracker to obtain more
|
|
|
|
|
information about a particular change.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
****************************************************************************
|
|
|
|
|
* Source incompatible changes *
|
|
|
|
|
****************************************************************************
|
|
|
|
|
|
2011-11-11 23:08:42 +00:00
|
|
|
|
2012-04-24 21:57:42 +00:00
|
|
|
- QObject
|
|
|
|
|
* The signatures of the connectNotify() and disconnectNotify() functions
|
|
|
|
|
have changed. The functions now get passed a QMetaMethod that identifies
|
|
|
|
|
the signal, rather than a const char *.
|
|
|
|
|
|
2011-06-27 14:05:22 +00:00
|
|
|
- QSslCertificate::subjectInfo() and QSslCertificate::issuerInfo() now
|
|
|
|
|
return a QStringList instead of a QString
|
|
|
|
|
|
2011-11-11 23:08:42 +00:00
|
|
|
- QSslCertificate::isValid() has been deprecated. Originally it only checked
|
|
|
|
|
the certificate dates, but later checking for blacklisting was added. Now
|
|
|
|
|
there's a more specific QSslCertificate::isBlacklisted() method.
|
|
|
|
|
|
2011-06-28 13:08:12 +00:00
|
|
|
- Unite clipping support has been removed from QPainter. The alternative is
|
|
|
|
|
to unite QRegion's and using the result on QPainter.
|
2011-06-27 14:05:22 +00:00
|
|
|
|
2011-07-21 16:47:26 +00:00
|
|
|
- QLibrary::resolve() now returns a function pointer instead of a void
|
|
|
|
|
pointer.
|
|
|
|
|
|
2011-08-03 16:36:55 +00:00
|
|
|
- QSslCertificate::alternateSubjectNames() is deprecated (but can be enabled
|
|
|
|
|
via QT_DISABLE_DEPRECATED_BEFORE), use
|
|
|
|
|
QSslCertificate::subjectAlternativeNames() instead.
|
|
|
|
|
|
2011-08-31 12:23:42 +00:00
|
|
|
- QLibraryInfo::buildKey() has been removed. Likewise, the QT_BUILD_KEY
|
|
|
|
|
preprocessor #define has also been removed. The build-key is obsolete
|
|
|
|
|
and is no longer necessary.
|
|
|
|
|
|
2011-09-19 18:26:25 +00:00
|
|
|
- QCoreApplication::translate() will no longer return the source text when
|
|
|
|
|
the translation is empty. Use lrelease -removeidentical for optimization.
|
2012-01-10 09:13:55 +00:00
|
|
|
|
2012-01-31 17:31:58 +00:00
|
|
|
- QString and QByteArray constructors that take a size argument will now treat
|
|
|
|
|
negative sizes to indicate nul-terminated strings (a nul-terminated array of
|
|
|
|
|
QChar, in the case of QString). In Qt 4, negative sizes were ignored and
|
|
|
|
|
result in empty QString and QByteArray, respectively. The size argument to
|
|
|
|
|
those constructors now has a default value of -1, thus replacing the separate
|
|
|
|
|
constructors that did the same.
|
|
|
|
|
|
2011-09-29 11:31:39 +00:00
|
|
|
- Qt::escape() is deprecated (but can be enabled via
|
|
|
|
|
QT_DISABLE_DEPRECATED_BEFORE), use QString::toHtmlEscaped() instead.
|
2011-09-19 18:26:25 +00:00
|
|
|
|
2012-01-20 10:22:09 +00:00
|
|
|
- QBool is gone. QString::contains, QByteArray::contains, and QList::contains
|
|
|
|
|
used to return an internal QBool class so that the Qt3 code
|
|
|
|
|
"if (a.contains() == 2)" wouldn't compile anymore. Such code cannot exist
|
|
|
|
|
in Qt4, so these methods return a bool now. If your code used the undocumented
|
|
|
|
|
QBool, simply replace it with bool.
|
|
|
|
|
|
2012-02-24 21:27:32 +00:00
|
|
|
- qIsDetached<> has been removed without replacement.
|
|
|
|
|
|
2012-02-03 11:54:25 +00:00
|
|
|
- QMetaType:
|
|
|
|
|
* QMetaType::construct() has been renamed to QMetaType::create().
|
|
|
|
|
* QMetaType::unregisterType() has been removed.
|
2011-10-06 11:25:58 +00:00
|
|
|
|
2012-03-20 18:27:02 +00:00
|
|
|
- QMetaMethod:
|
|
|
|
|
* QMetaMethod::signature() has been renamed to QMetaMethod::methodSignature(),
|
|
|
|
|
and the return type has been changed to QByteArray. This was done to be able
|
|
|
|
|
to generate the signature string on demand, rather than always storing it in
|
|
|
|
|
the meta-data.
|
|
|
|
|
* QMetaMethod::typeName() no longer returns an empty string when the return
|
|
|
|
|
type is void; it returns "void". The recommended way of checking whether a
|
|
|
|
|
method returns void is to compare the return value of QMetaMethod::returnType()
|
|
|
|
|
to QMetaType::Void.
|
2012-02-18 22:16:24 +00:00
|
|
|
|
2012-04-13 12:52:34 +00:00
|
|
|
- QVariant:
|
|
|
|
|
* Inconsistent constructor taking Qt::GlobalColor and producing QVariant(QColor)
|
|
|
|
|
instance was removed. Code constructing such variants can be migrated by
|
|
|
|
|
explicitly calling QColor constructor. For example from "QVariant(Qt::red)"
|
|
|
|
|
to "QVariant(QColor(Qt::red))"
|
|
|
|
|
|
2011-10-28 02:04:53 +00:00
|
|
|
- QTestLib:
|
testlib: Count passes, fails and skips consistently.
For data-driven tests, testlib previously counted one fail or skip for
each data row that failed or skipped, while it counted only one pass
for a test function where all rows passed and counted no passes for a
test function where some rows passed and some rows failed. A similar
problem also existed for benchmark tests, which could run multiple
iterations of the same test, with each fail and skip being counted but
only a single pass being counted for the entire series of iterations.
This commit makes testlib count one pass, fail or skip for each data
row. Test functions that are not data-driven count one result for the
test function, as before. Benchmark tests count one pass, fail or skip
per iteration.
A side-effect of this change is that the test output in plain text, xml
and light xml formats now shows a result for every data row and
benchmark iteration executed, allowing post-processors to correctly
calculate the total number of tests executed. Previously, individual
rows were not shown in the test output if they passed, making such
calculations impossible.
The only change to the xunitxml output format is to correct a bug where
no test result was recorded for a test function if the last data row
was skipped and all other rows passed -- in which case the overall
result should be a pass. Note that there is also a pre-existing bug
in the xunit logger, where no result is reported if all rows are
skipped; that bug is unaffected by this commit.
Task-number: QTBUG-21848
Task-number: QTBUG-22124
Change-Id: I7e17177e10d6e89e55b9684c159bd506f21d002b
Reviewed-by: Ed Baak <ed.baak@nokia.com>
2012-02-02 07:08:44 +00:00
|
|
|
* The plain-text, xml and lightxml test output formats have been changed to
|
|
|
|
|
show a test result for every row of test data in data-driven tests. In
|
|
|
|
|
Qt4, only fails and skips were shown for individual data rows and passes
|
|
|
|
|
were not shown for individual data rows, preventing accurate calculation
|
|
|
|
|
of test run rates and pass rates.
|
2011-10-28 02:04:53 +00:00
|
|
|
* The QTRY_VERIFY and QTRY_COMPARE macros have been moved into QTestLib.
|
|
|
|
|
These macros formerly lived in tests/shared/util.h but are now provided
|
2012-01-10 09:13:55 +00:00
|
|
|
by including the <QtTest/QtTest> header. In addition,
|
|
|
|
|
QTRY_VERIFY_WITH_TIMEOUT and QTRY_COMPARE_WITH_TIMEOUT are provided,
|
|
|
|
|
allowing for specifying custom timeout values.
|
2011-10-28 02:04:53 +00:00
|
|
|
* The QTEST_NOOP_MAIN macro has been removed from the API. If a test is
|
|
|
|
|
known at compile-time to be inapplicable for a particular build it should
|
|
|
|
|
be omitted via .pro file logic, or the test should call QSKIP in the
|
|
|
|
|
initTestCase() method to skip the entire test and report a meaningful
|
|
|
|
|
explanation in the test log.
|
|
|
|
|
* The DEPENDS_ON macro has been removed from the API. This macro did nothing
|
|
|
|
|
and misled some users to believe that they could make test functions depend
|
|
|
|
|
on each other or impose an execution order on test functions.
|
2011-12-12 02:43:18 +00:00
|
|
|
* The QTest::qt_snprintf function has been removed from the API. This was an
|
|
|
|
|
internal testlib function that was exposed in the public API due to its use
|
|
|
|
|
in a public macro. Any calls to this function should be replaced by a call
|
|
|
|
|
to qsnprintf(), which comes from the <QtCore/QByteArray> header.
|
2011-12-19 05:22:51 +00:00
|
|
|
* The QTest::pixmapsAreEqual() function has been removed from the API.
|
|
|
|
|
Comparison of QPixmap objects should be done using QCOMPARE, which provides
|
|
|
|
|
more informative output in the event of a failure.
|
2011-10-28 02:04:53 +00:00
|
|
|
* The QSKIP macro no longer has the "mode" parameter, which caused problems
|
|
|
|
|
for calculating test metrics, as the SkipAll mode hid information about
|
|
|
|
|
what test data was skipped. Calling QSKIP in a test function now behaves
|
|
|
|
|
like SkipSingle -- skipping a non-data-driven test function or skipping
|
|
|
|
|
only the current data row of a data-driven test function. Every skipped
|
|
|
|
|
data row is now reported in the test log.
|
|
|
|
|
|
2011-11-14 11:33:55 +00:00
|
|
|
- The QSsl::TlsV1 enum value was renamed to QSsl::TlsV1_0 .
|
|
|
|
|
|
2011-11-22 13:33:15 +00:00
|
|
|
- QAccessible:
|
|
|
|
|
* Internal QAccessible::State enum value HasInvokeExtension removed
|
|
|
|
|
- QAccessibleInterface:
|
|
|
|
|
* The "child" integer parameters have been removed. This moves the api
|
|
|
|
|
to be closer to IAccessible2.
|
|
|
|
|
This means several functions lose their integer parameter:
|
|
|
|
|
text(Text t, int child) -> text(Text t), rect(int child) -> rect()
|
|
|
|
|
setText(Text t, int child, const QString &text) -> setText(Text t, const QString &text)
|
|
|
|
|
role(int child) -> role(), state(int child) -> state()
|
2012-02-20 10:19:10 +00:00
|
|
|
* parent() and child() was added in order to do hierarchical navigation.
|
|
|
|
|
* relations() was added as a replacement to relationTo()
|
|
|
|
|
* As a consequence of the above two points, navigate() was removed.
|
2011-11-22 13:33:15 +00:00
|
|
|
* Accessible-Action related functions have been removed. QAccessibleInterface
|
|
|
|
|
subclasses are expected to implement the QAccessibleActionInterface instead.
|
|
|
|
|
These functions have been removed:
|
|
|
|
|
QAccessibleInterface::userActionCount, QAccessibleInterface::actionText,
|
|
|
|
|
QAccessibleInterface::doAction
|
|
|
|
|
- QAccessibleEvent also loses the child parameter.
|
|
|
|
|
QAccessibleEvent(Type type, int child) -> QAccessibleEvent(Type type)
|
|
|
|
|
QAccessibleEvent::child() removed.
|
|
|
|
|
- QAccessibleActionInterface:
|
|
|
|
|
* Refactored to be based on action names. All functions have been changed from using
|
|
|
|
|
int parameters to strings.
|
|
|
|
|
|
2011-11-30 13:58:53 +00:00
|
|
|
- QSound has been moved from QtGui to QtMultimedia
|
|
|
|
|
|
2011-08-11 14:23:10 +00:00
|
|
|
- QTabletEvent::QTabletEvent does not take a hiResGlobalPos argument anymore,
|
|
|
|
|
as all coordinates are floating point based now.
|
|
|
|
|
|
2011-11-27 15:42:23 +00:00
|
|
|
- QTouchEvent:
|
|
|
|
|
|
|
|
|
|
* The DeviceType enum and deviceType() have been deprecated due to
|
|
|
|
|
the introduction of QTouchDevice.
|
|
|
|
|
|
|
|
|
|
* The signature of the constructor has changed. It now takes a
|
|
|
|
|
QTouchDevice pointer instead of just a DeviceType value.
|
|
|
|
|
|
|
|
|
|
* TouchPointState no longer includes TouchPointStateMask and
|
2012-01-13 15:21:40 +00:00
|
|
|
TouchPointPrimary. QTouchEvent::TouchPoint::isPrimary() has
|
|
|
|
|
been removed.
|
2011-11-27 15:42:23 +00:00
|
|
|
|
|
|
|
|
* QWidget *widget() has been removed and is replaced by QObject
|
|
|
|
|
*target() in order to avoid QWidget dependencies.
|
|
|
|
|
|
2012-02-10 14:40:06 +00:00
|
|
|
* QEvent::TouchCancel has been introduced. On systems where it makes
|
|
|
|
|
sense this event type can be used to differentiate between a
|
|
|
|
|
regular TouchEnd and abrupt touch sequence cancellations caused by
|
|
|
|
|
the compositor, for example when a system gesture gets recognized.
|
|
|
|
|
|
2011-12-30 11:00:09 +00:00
|
|
|
- QMetaType
|
|
|
|
|
|
2012-02-01 11:58:31 +00:00
|
|
|
* Q_DECLARE_METATYPE(Foo*) now requires that Foo is fully defined. In
|
|
|
|
|
cases where a forward declared type should be used as a metatype,
|
|
|
|
|
Q_DECLARE_OPAQUE_POINTER(Foo*) can be used to allow that.
|
2011-12-30 11:00:09 +00:00
|
|
|
|
2012-01-27 02:33:13 +00:00
|
|
|
- QItemEditorFactory
|
|
|
|
|
|
|
|
|
|
* The signature of the createEditor and valuePropertyName methods
|
|
|
|
|
have been changed to take arguments of type int instead of QVariant::Type.
|
|
|
|
|
|
2011-11-27 15:42:23 +00:00
|
|
|
- QWindowSystemInterface:
|
|
|
|
|
|
|
|
|
|
* The signature of all handleTouchEvent() variants have changed,
|
|
|
|
|
taking a QTouchDevice* instead of just a DeviceType value.
|
|
|
|
|
Platform or generic plug-ins have to create and register at least
|
|
|
|
|
one QTouchDevice before sending the first touch event.
|
|
|
|
|
|
|
|
|
|
* The event type parameter is removed from handleTouchEvent().
|
|
|
|
|
|
2011-12-10 14:30:18 +00:00
|
|
|
- The previously exported function qt_translateRawTouchEvent() has been removed.
|
|
|
|
|
Use QWindowSystemInterface::handleTouchEvent() instead.
|
|
|
|
|
|
2011-12-21 10:33:33 +00:00
|
|
|
- QAbstractEventDispatcher
|
|
|
|
|
|
|
|
|
|
* The signature for the pure-virtual registerTimer() has changed. Subclasses
|
|
|
|
|
of QAbstractEventDispatcher will need to be updated to reimplement the new
|
|
|
|
|
pure-virtual 'virtual void registerTimer(int timerId, int interval,
|
|
|
|
|
Qt::TimerType timerType, QObject *object) = 0;'
|
|
|
|
|
|
|
|
|
|
* QAbstractEventDispatcher::TimerInfo is no longer a QPair<int, int>. It is
|
|
|
|
|
now a struct with 3 members: struct TimerInfo { int timerId; int interval;
|
|
|
|
|
Qt::TimerType timerType; }; Reimplementations of
|
|
|
|
|
QAbstractEventDispatcher::registeredTimers() will need to be updated to pass
|
|
|
|
|
3 arguments to the TimerInfo constructor (instead of 2).
|
2011-12-10 14:30:18 +00:00
|
|
|
|
2012-01-02 15:47:59 +00:00
|
|
|
- QUuid
|
|
|
|
|
|
|
|
|
|
* Removed implicit conversion operator QUuid::operator QString(), instead
|
|
|
|
|
QUuid::toString() function should be used.
|
|
|
|
|
|
2011-12-22 19:42:49 +00:00
|
|
|
- The QHttp, QHttpHeader, QHttpResponseHeader and QHttpRequestHeader classes have
|
|
|
|
|
been removed, QNetworkAccessManager should be used instead.
|
|
|
|
|
|
2012-01-11 12:48:08 +00:00
|
|
|
- The QFtp class is no longer exported, QNetworkAccessManager should be used
|
|
|
|
|
instead.
|
|
|
|
|
|
2012-01-05 17:24:53 +00:00
|
|
|
- QProcess
|
|
|
|
|
|
|
|
|
|
* On Windows, QProcess::ForwardedChannels will not forward the output of GUI
|
|
|
|
|
applications anymore, if they do not create a console.
|
2011-12-22 19:42:49 +00:00
|
|
|
|
2011-12-29 14:47:21 +00:00
|
|
|
- QAbstractSocket's connectToHost() and disconnectFromHost() are now virtual and
|
|
|
|
|
connectToHostImplementation() and disconnectFromHostImplementation() don't exist.
|
|
|
|
|
|
2012-01-11 15:06:14 +00:00
|
|
|
- QTcpServer::incomingConnection() now takes a qintptr instead of an int.
|
|
|
|
|
|
2012-01-17 13:57:55 +00:00
|
|
|
- QNetworkConfiguration::bearerName() removed, and bearerTypeName() should be used.
|
|
|
|
|
|
2012-01-19 09:29:41 +00:00
|
|
|
- QDir::convertSeparators() (deprecated since Qt 4.2) has been removed. Use
|
|
|
|
|
QDir::toNativeSeparators() instead.
|
2011-11-15 08:34:38 +00:00
|
|
|
|
2012-01-25 12:58:17 +00:00
|
|
|
- QIconEngineV2 was merged into QIconEngine
|
|
|
|
|
You might need to adjust your code if it used a QIconEngine.
|
|
|
|
|
|
2012-01-19 09:29:41 +00:00
|
|
|
- qmake
|
2012-02-02 17:11:16 +00:00
|
|
|
* Projects which explicitly set an empty TARGET are considered broken now.
|
2012-02-21 11:56:47 +00:00
|
|
|
* The makespec and .qmake.cache do not see build pass specific variables any more.
|
2012-02-21 21:23:48 +00:00
|
|
|
* load()/include() with a target namespace and infile()/$$fromfile() now start with
|
|
|
|
|
an entirely pristine context.
|
2012-02-28 19:57:38 +00:00
|
|
|
* Configure's -sysroot and -hostprefix are now handled slightly differently.
|
|
|
|
|
The QT_INSTALL_... properties are now automatically prefixed with the sysroot;
|
2012-03-09 18:11:27 +00:00
|
|
|
the raw values are available as QT_INSTALL_.../raw and the sysroot as QT_SYSROOT.
|
2012-02-28 19:57:38 +00:00
|
|
|
The new QT_HOST_... properties can be used to refer to the Qt host tools.
|
2012-02-21 11:56:47 +00:00
|
|
|
* Several functions and built-in variables were modified to return normalized paths.
|
2012-05-09 16:52:44 +00:00
|
|
|
* The -(no-)exception flags in configure have been removed. Qt modules are now compiled
|
|
|
|
|
without exceptions by default, as they do not use them and can neither handle them
|
|
|
|
|
properly. Qt Core still has exceptions enabled to correctly throw bad_alloc exceptions
|
|
|
|
|
in our tool classes.
|
|
|
|
|
Whether code should be compiled with exception support enabled or disabled can be
|
|
|
|
|
controlled by a CONFIG += exceptions/exceptions_off setting in the .pro file.
|
2011-12-29 14:47:21 +00:00
|
|
|
|
2012-01-12 09:43:29 +00:00
|
|
|
- QTextCodecPlugin has been removed since it is no longer used. All text codecs
|
|
|
|
|
are now built into QtCore.
|
2012-01-19 09:29:41 +00:00
|
|
|
|
2012-01-30 13:09:13 +00:00
|
|
|
- QDir::NoDotAndDotDot is QDir::NoDot|QDir::NoDotDot therefore there is no need
|
|
|
|
|
to use or check both.
|
|
|
|
|
|
2012-02-17 19:09:17 +00:00
|
|
|
- QFSFileEngine, QAbstractFileEngine, QAbstractFileEngineIterator and
|
|
|
|
|
QAbstractFileEngineHandler were removed from public API and are no longer
|
|
|
|
|
exported. They may temporarily live as private implementation details, but
|
|
|
|
|
they may be altogether dropped or otherwise changed at will in the future.
|
|
|
|
|
|
2012-01-27 19:04:42 +00:00
|
|
|
- QLocale
|
|
|
|
|
* toShort(), toUShort(), toInt(), toUInt(), toLongLong() and toULongLong() no
|
|
|
|
|
longer take a parameter for base, they will only perform localised base 10
|
|
|
|
|
conversions. For converting other bases use the QString methods instead.
|
|
|
|
|
|
2012-01-27 20:21:21 +00:00
|
|
|
- QSystemLocale has been removed from the public API.
|
|
|
|
|
|
2012-04-02 20:02:31 +00:00
|
|
|
- QSqlQueryModel::indexInQuery() is now virtual. See note below under QtSql.
|
2012-02-09 13:53:35 +00:00
|
|
|
|
2012-03-22 20:27:26 +00:00
|
|
|
- QSqlDriver::subscribeToNotification, unsubscribeFromNotification,
|
|
|
|
|
subscribedToNotifications, isIdentifierEscaped, and stripDelimiters
|
|
|
|
|
are now virtual. See note below under QtSql.
|
|
|
|
|
|
2012-02-20 08:43:02 +00:00
|
|
|
- qMacVersion() has been removed. Use QSysInfo::macVersion() or
|
|
|
|
|
QSysInfo::MacintoshVersion instead.
|
|
|
|
|
|
2012-04-11 12:22:26 +00:00
|
|
|
- QColorDialog::customColor() now returns a QColor value instead of QRgb.
|
|
|
|
|
QColorDialog::setCustomColor() and QColorDialog::setStandardColor() now
|
|
|
|
|
take a QColor value for their second parameter instead of QRgb.
|
|
|
|
|
|
2011-06-27 14:05:22 +00:00
|
|
|
****************************************************************************
|
|
|
|
|
* General *
|
|
|
|
|
****************************************************************************
|
|
|
|
|
|
|
|
|
|
General Improvements
|
|
|
|
|
--------------------
|
|
|
|
|
|
2011-10-28 02:04:53 +00:00
|
|
|
- The directory structure of the qtbase unit-tests has been reworked to
|
|
|
|
|
more closely match the directory structure of the code under test.
|
|
|
|
|
Integration tests have been moved to tests/auto/integrationtests.
|
2011-06-27 14:05:22 +00:00
|
|
|
|
2012-05-29 05:10:09 +00:00
|
|
|
- Qt is compiled with C++11 support enabled by default, provided the compiler
|
|
|
|
|
supports C++11. Qmake based projects can enable C++11 support explicitly
|
|
|
|
|
using 'CONFIG+=c++11' in their .pro files. To enable it conditionally, use
|
|
|
|
|
'contains(QT_CONFIG,c++11):CONFIG+=c++11'. This will enable C++11 support
|
|
|
|
|
only if Qt was built with C++11 support.
|
|
|
|
|
|
2011-06-27 14:05:22 +00:00
|
|
|
Third party components
|
|
|
|
|
----------------------
|
|
|
|
|
|
2012-04-30 12:24:34 +00:00
|
|
|
- SQLITE_ENABLE_FTS3,SQLITE_ENABLE_FTS3_PARENTHESIS and SQLITE_ENABLE_RTREE
|
|
|
|
|
flags are now enabled by default on all platforms, for the sqlite3 copy under
|
|
|
|
|
the 3rdparty directory.
|
2011-06-27 14:05:22 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
****************************************************************************
|
|
|
|
|
* Library *
|
|
|
|
|
****************************************************************************
|
|
|
|
|
|
|
|
|
|
QtCore
|
|
|
|
|
------
|
2011-07-08 14:24:57 +00:00
|
|
|
* drop a bogus QChar::NoCategory enum value; the proper QChar::Other_NotAssigned
|
|
|
|
|
value is returned for an unassigned codepoints now.
|
2011-06-27 14:05:22 +00:00
|
|
|
|
2011-11-24 22:21:36 +00:00
|
|
|
* layoutAboutToBeChanged is no longer emitted by QAbstractItemModel::beginMoveRows.
|
|
|
|
|
layoutChanged is no longer emitted by QAbstractItemModel::endMoveRows. Proxy models
|
|
|
|
|
should now also connect to (and disconnect from) the rowsAboutToBeMoved and
|
|
|
|
|
rowsMoved signals.
|
|
|
|
|
|
2011-12-20 11:56:01 +00:00
|
|
|
* The default value of the property QSortFilterProxyModel::dynamicSortFilter was
|
|
|
|
|
changed from false to true.
|
|
|
|
|
|
2011-12-15 15:31:21 +00:00
|
|
|
* The signature of the virtual QAbstractItemView::dataChanged method has changed to
|
|
|
|
|
include the roles which have changed. The signature is consistent with the dataChanged
|
|
|
|
|
signal in the model.
|
|
|
|
|
|
2011-12-27 21:30:05 +00:00
|
|
|
* QFileSystemWatcher is now able to return failure in case of errors whilst
|
|
|
|
|
altering the watchlist in both the singular and QStringList overloads of
|
|
|
|
|
addPath and removePath.
|
|
|
|
|
|
2012-01-23 12:02:36 +00:00
|
|
|
* QString::mid, QString::midRef and QByteArray::mid, if the position passed
|
|
|
|
|
is equal to the length (that is, right after the last character/byte),
|
|
|
|
|
now return an empty QString, QStringRef or QByteArray respectively.
|
|
|
|
|
in Qt 4 they returned a null QString or a null QStringRef.
|
|
|
|
|
|
2012-01-22 21:23:50 +00:00
|
|
|
* QString methods toLongLong(), toULongLong(), toLong(), toULong(), toInt(),
|
|
|
|
|
toUInt(), toShort(), toUShort(), toDouble(), and toFloat() no longer use the
|
|
|
|
|
default or system locale, they will always use the C locale. This is to
|
|
|
|
|
guarantee consistent default conversion of strings. For locale-aware conversions
|
|
|
|
|
use the equivalent QLocale methods.
|
|
|
|
|
|
2012-01-16 20:20:39 +00:00
|
|
|
* QDate, QTime, and QDateTime have undergone important behavioural changes:
|
2012-01-09 20:50:00 +00:00
|
|
|
* QDate only implements the Gregorian calendar, the switch to the Julian
|
|
|
|
|
calendar before 1582 has been removed. This means all QDate methods will
|
|
|
|
|
return different results for dates prior to 15 October 1582, and there is
|
|
|
|
|
no longer a gap between 4 October 1582 and 15 October 1582.
|
2012-01-16 20:20:39 +00:00
|
|
|
* QDate::setYMD() is deprecated, use QDate::setDate() instead
|
2011-07-17 18:30:12 +00:00
|
|
|
* Most methods now apply strict validity checks and will return appropriate
|
|
|
|
|
and consistent values when invalid. For example, QDate::year() will return
|
|
|
|
|
0 and QDate::shortMonthName() will return QString().
|
|
|
|
|
* Adding days to a null QDate or seconds to a null QTime will no longer return
|
|
|
|
|
a valid QDate/QTime.
|
2011-08-25 06:54:16 +00:00
|
|
|
* QDate stores the Julian Day as a qint64 extending date support across a
|
|
|
|
|
more interesting range, see the class documentation for details.
|
|
|
|
|
* Conversion to YMD form dates is only accurate between to 4800 BCE to
|
|
|
|
|
1.4 million CE
|
|
|
|
|
* The QDate::addDays() and QDateTime::addDays() methods now take a qint64
|
|
|
|
|
* The QDate::daysTo() and QDateTime::daysTo() methods now return a qint64
|
2012-01-16 20:20:39 +00:00
|
|
|
|
2012-01-30 12:23:22 +00:00
|
|
|
* QTextCodec::codecForCStrings() and QTextCodec::setCodecForCStrings() have both
|
|
|
|
|
been removed. This was removed due to issues with breaking other code from
|
|
|
|
|
libraries, creating uncertainty/bugs in using QString easily, and (to a lesser
|
|
|
|
|
extent) performance issues.
|
2012-01-16 20:20:39 +00:00
|
|
|
|
2012-05-16 21:09:56 +00:00
|
|
|
* QTextCodec::codecForTr() and QTextCodec::setCodecForTr() have been removed.
|
|
|
|
|
QObject::trUtf8 and QCoreApplication::Encoding enum are now obsolete. Qt assumes
|
|
|
|
|
that the source code is encoded in UTF-8.
|
2012-01-31 22:33:30 +00:00
|
|
|
|
2012-05-14 13:43:57 +00:00
|
|
|
* QFile::setEncodingFunction and QFile::setDecodingFunction are obsolete and do
|
|
|
|
|
nothing in Qt 5. The QFile::encodeName and QFile::decodeName functions are now
|
|
|
|
|
hardcoded to operate on QString::fromLocal8Bit and QString::toLocal8Bit
|
|
|
|
|
only. Therefore, it's still possible to obtain the old behaviour by calling
|
|
|
|
|
QTextCodec::setCodecForLocale. However, that is not recommended: new code
|
|
|
|
|
should not make assumptions about the filesystem encoding and older code should
|
|
|
|
|
have those assumptions removed.
|
|
|
|
|
|
2012-01-23 22:34:09 +00:00
|
|
|
* QIntValidator and QDoubleValidator no longer fall back to using the C locale if
|
|
|
|
|
the requested locale fails to validate the input.
|
|
|
|
|
|
2012-01-23 22:47:59 +00:00
|
|
|
* A new set of classes for doing pattern matching with Perl-compatible regular
|
|
|
|
|
expressions has been added: QRegularExpression, QRegularExpressionMatch and
|
|
|
|
|
QRegularExpressionMatchIterator. They aim to replace QRegExp with a more
|
|
|
|
|
powerful and flexible regular expression engine.
|
|
|
|
|
|
2012-02-14 10:17:36 +00:00
|
|
|
* QEvent::AccessibilityPrepare, AccessibilityHelp and AccessibilityDescription removed:
|
|
|
|
|
* The enum values simply didn't make sense in the first place and should simply be dropped.
|
|
|
|
|
|
2012-03-24 08:50:02 +00:00
|
|
|
* [QTBUG-23529] QHash is now more resilient to a family of denial of service
|
|
|
|
|
attacks exploiting algorithmic complexity, by supporting two-arguments overloads
|
|
|
|
|
of the qHash() hashing function.
|
|
|
|
|
|
2011-06-27 14:05:22 +00:00
|
|
|
QtGui
|
|
|
|
|
-----
|
2011-11-22 13:33:15 +00:00
|
|
|
* Accessibility has been refactored. The hierachy of accessible objects is implemented via
|
|
|
|
|
proper parent/child functions instead of using navigate which has been deprecated for this purpose.
|
|
|
|
|
Table and cell interfaces have been added to qaccessible2.h
|
|
|
|
|
|
2011-11-27 15:42:23 +00:00
|
|
|
* Touch events and points have been extended to hold additional
|
|
|
|
|
information like capability flags, point-specific flags, velocity,
|
|
|
|
|
and raw positions.
|
2011-06-27 14:05:22 +00:00
|
|
|
|
2012-03-16 08:01:50 +00:00
|
|
|
* A new set of enabler classes have been added, most importantly QWindow, QScreen,
|
|
|
|
|
QSurfaceFormat, and QOpenGLContext.
|
|
|
|
|
|
|
|
|
|
* Most of the useful QtOpenGL classes have been polished and moved into
|
|
|
|
|
QtGui. See QOpenGLFramebufferObject, QOpenGLShaderProgram,
|
|
|
|
|
QOpenGLFunctions, etc.
|
|
|
|
|
|
|
|
|
|
* QOpenGLPaintDevice has been added to be able to use QPainter to render into
|
|
|
|
|
the currently bound context.
|
|
|
|
|
|
2011-09-23 12:28:19 +00:00
|
|
|
QtWidgets
|
|
|
|
|
---------
|
2012-02-01 07:43:18 +00:00
|
|
|
* QInputContext removed as well as related getters and setters on QWidget and QApplication.
|
2012-01-02 15:42:00 +00:00
|
|
|
Input contexts are now platform specific.
|
2011-09-23 12:28:19 +00:00
|
|
|
|
2012-01-20 00:30:02 +00:00
|
|
|
* QInputDialog::getInteger() has been obsoleted. Use QInputDialog::getInt() instead.
|
|
|
|
|
|
Merge QStyleOption*V{2,3,4} classes together
In order to keep binary compatibility, Qt 4 introduced V{2,3,4}
classes for QStyleOption subclasses. They're simple, low level
containers for various members with public access (no accessors
required).
In Qt 5.0 we can break BC, so this patch moves the members
from the derived classes into the ``base'' ones.
The ``base'' ones get a version bump matching the highest
version available, and the V{2,3,4} classes become typedefs.
This change can cause problems in code that used QStyleOption
directly, especially QStyleOptionViewItem, because the old V4
fields get default initialization but the QStyle subclasses
detect that the option is a V4 option and expect all fields
to be properly initialized. The fix in such places is to
properly initialize all fields.
Task-number: QTBUG-23522
Change-Id: I2f782da09ca5cc8c4cbafc07448fb0d33153a251
Reviewed-by: Lars Knoll <lars.knoll@nokia.com>
2012-01-30 00:52:34 +00:00
|
|
|
* In Qt 4, many QStyleOption subclasses were introduced in order to keep
|
|
|
|
|
binary compatibility -- QStyleOption was designed to be extended this way,
|
|
|
|
|
in fact it embeds a version number. In Qt 5 the various QStyleOption*V{2,3,4}
|
|
|
|
|
classes have been removed, and their members merged into the respective
|
|
|
|
|
base classes. Those classes were left as typedefs to keep existing code
|
|
|
|
|
working. Still, some minor adjustements could be necessary, especially in code
|
|
|
|
|
that uses QStyleOption directly and does not initialize all the members using
|
|
|
|
|
the proper Qt API: due to the version bump, QStyle will try to use the additional
|
|
|
|
|
QStyleOption members, which are left default-initialized.
|
|
|
|
|
|
2012-03-03 05:05:54 +00:00
|
|
|
* QHeaderView - The following functions have been obsoleted.
|
|
|
|
|
|
|
|
|
|
* void setMovable(bool movable) - use void setSectionsMovable(bool movable) instead.
|
|
|
|
|
|
|
|
|
|
* bool isMovable() const - use bool sectionsMovable() const instead.
|
|
|
|
|
|
|
|
|
|
* void setClickable(bool clickable) - use void setSectionsClickable(bool clickable) instead.
|
|
|
|
|
|
|
|
|
|
* bool isClickable() const - use bool sectionsClickable() instead.
|
|
|
|
|
|
|
|
|
|
* void setResizeMode(int logicalindex, ResizeMode mode) -
|
|
|
|
|
use setSectionResizeMode(logicalindex, mode) instead.
|
|
|
|
|
|
|
|
|
|
* ResizeMode resizeMode(int logicalindex) const -
|
|
|
|
|
use sectionResizeMode(int logicalindex) instead.
|
|
|
|
|
|
2012-03-21 19:41:57 +00:00
|
|
|
* QDateEdit and QTimeEdit have re-gained a USER property. These were originally removed
|
|
|
|
|
before Qt 4.7.0, and are re-added for 5.0. This means that the userProperty for
|
|
|
|
|
those classes are now QDate and QTime respectively, not QDateTime as they have been
|
|
|
|
|
for the 4.7 and 4.8 releases.
|
|
|
|
|
|
2011-06-27 14:05:22 +00:00
|
|
|
QtNetwork
|
|
|
|
|
---------
|
2011-10-24 10:01:09 +00:00
|
|
|
* QHostAddress::isLoopback() API added. Returns true if the address is
|
|
|
|
|
one of the IP loopback addresses.
|
2011-06-27 14:05:22 +00:00
|
|
|
|
2011-11-10 22:37:16 +00:00
|
|
|
* QSslCertificate::serialNumber() now always returns the serial number in
|
|
|
|
|
hexadecimal format.
|
|
|
|
|
|
2011-12-27 16:09:59 +00:00
|
|
|
* The openssl network backend now reads the ssl configuration file allowing
|
|
|
|
|
the use of openssl engines.
|
|
|
|
|
|
2012-03-29 14:11:03 +00:00
|
|
|
QtDBus
|
|
|
|
|
------
|
|
|
|
|
* QtDBus now generates property annotations for the Qt type names
|
|
|
|
|
in the org.qtproject.QtDBus namespace. When parsing such annotations
|
|
|
|
|
both the old and new namespaces are accepted.
|
|
|
|
|
|
|
|
|
|
* QtDBus error codes have been updated to be on the org.qtproject.QtDBus.Error
|
|
|
|
|
namespace.
|
2011-11-10 22:37:16 +00:00
|
|
|
|
2011-06-27 14:05:22 +00:00
|
|
|
QtOpenGL
|
|
|
|
|
--------
|
|
|
|
|
|
2012-03-16 08:01:50 +00:00
|
|
|
* Most of the classes in this module (with the notable exception of QGLWidget)
|
|
|
|
|
now have equivalents in QtGui, along with the naming change QGL -> QOpenGL.
|
|
|
|
|
The classes in QtOpenGL that have equivalents in QtGui can now be considered
|
|
|
|
|
deprecated.
|
|
|
|
|
|
2011-06-27 14:05:22 +00:00
|
|
|
QtScript
|
|
|
|
|
--------
|
|
|
|
|
|
|
|
|
|
|
2011-10-28 02:04:53 +00:00
|
|
|
QTestLib
|
|
|
|
|
--------
|
|
|
|
|
* [QTBUG-20615] Autotests can now log test output to multiple destinations
|
|
|
|
|
and log formats simultaneously.
|
|
|
|
|
|
2012-02-06 13:04:26 +00:00
|
|
|
QtSql
|
|
|
|
|
-----
|
2012-04-22 23:06:17 +00:00
|
|
|
QSqlQueryModel/QSqlTableModel/QSqlRelationalTableModel
|
2012-02-06 13:04:26 +00:00
|
|
|
|
|
|
|
|
* The dataChanged() signal is now emitted for changes made to an inserted
|
|
|
|
|
record that has not yet been committed. Previously, dataChanged() was
|
|
|
|
|
suppressed in this case for OnRowChange and OnFieldChange. This was probably
|
|
|
|
|
an attempt to avoid trouble if setData() was called while handling
|
|
|
|
|
primeInsert(). By emitting dataChanged(), we ensure that all views are aware
|
|
|
|
|
of the change.
|
|
|
|
|
|
|
|
|
|
* While handling primeInsert() signal, the record must be manipulated using
|
|
|
|
|
the provided reference. Do not attempt to manipulate the records using the
|
|
|
|
|
model methods setData() or setRecord().
|
2011-10-28 02:04:53 +00:00
|
|
|
|
2012-02-06 16:02:32 +00:00
|
|
|
* removeRows() no longer emits extra beforeDelete signal for out of range row.
|
|
|
|
|
|
2012-02-06 16:19:19 +00:00
|
|
|
* removeRows() now requires the whole range of targetted rows to be valid
|
|
|
|
|
before doing anything. Previously, it would remove what it could and
|
|
|
|
|
ignore the rest of the range.
|
|
|
|
|
|
2012-03-15 10:23:27 +00:00
|
|
|
* removeRows(), for OnFieldChange and OnRowChange, allows only 1 row to be
|
|
|
|
|
removed and only if there are no other changed rows.
|
|
|
|
|
|
2012-02-07 23:16:46 +00:00
|
|
|
* setRecord() and insertRecord()
|
|
|
|
|
-Only use fields where generated flag is set to true. This is
|
|
|
|
|
is consistent with the meaning of the flag.
|
|
|
|
|
-Require all fields to map correctly. Previously fields that didn't
|
|
|
|
|
map were simply ignored.
|
2012-02-07 23:45:47 +00:00
|
|
|
-For OnManualSubmit, insertRecord() no longer leaves behind an empty
|
|
|
|
|
row if setRecord() fails.
|
QSqlTableModel::setData()/setRecord(): fix incorrect row
For OnFieldChange and OnRowChange, before submitting new changes,
setData() and setRecord() attempt to submit pending changes and
revert them upon failure. However, they fail to consider that
reverting pending insertions removes rows from the model. As a
result, the new change can be applied to a row higher than intended.
One possible solution would be to adjust the targetted index for the
removed rows, so that the intended row is affected by the new change.
But this still causes the strange editing experience as rows jump
up just as they are being edited.
It does not seem right in the first place for the model to initiate
reverting changes. It should be up to the application to decide what
to do when data cannot be committed. In particular, setData() and
setRecord() should not have the side effect of reverting already
pending changes.
The chosen solution is simply to refuse new changes that don't make
sense for the edit strategy. For OnFieldChange, flag() will
indicate read-only when editing is blocked by a pending change.
Since setData() and setRecord() submit data immediately for
OnFieldChange, it no longer makes sense to resubmit changes
automatically before a new change.
For OnRowChange, setData() keeps the behavior of automatically
submitting a pending row before starting on a new row. This is
historical behavior and is probably motivated by the fact that
QTableView does not automatically call submit() when editing leaves a
row. The obvious shortcoming of this is that the last row to be edited
will not be submitted automatically. It also prevents us from flagging
rows other than the pending row as read-only.
For OnRowChange, setRecord(), being row-oriented by nature, should
submit the change immediately rather than waiting for the next call
to setRecord(). This makes setRecord() consistent with insertRecord().
Change-Id: Icb4019d8b7c53a7ee48f8121a7a525e8bc35d523
Reviewed-by: Honglei Zhang <honglei.zhang@nokia.com>
2012-02-28 22:41:31 +00:00
|
|
|
-setRecord() now automatically submits for OnRowChange.
|
2012-02-06 16:19:19 +00:00
|
|
|
|
2012-02-09 13:53:35 +00:00
|
|
|
* QSqlQueryModel::indexInQuery() is now virtual. See
|
|
|
|
|
QSqlTableModel::indexInQuery() as example of how to implement in a
|
|
|
|
|
subclass.
|
2011-10-28 02:04:53 +00:00
|
|
|
|
2012-04-22 23:06:17 +00:00
|
|
|
* QSqlQueryMode::setQuery() emits fewer signals. The modelAboutToBeReset()
|
|
|
|
|
and modelReset() signals suffice to inform views that they must reinterrogate
|
|
|
|
|
the model.
|
|
|
|
|
|
2012-03-06 23:24:08 +00:00
|
|
|
* QSqlTableModel::selectRow(): This is a new method that refreshes a single
|
|
|
|
|
row in the model from the database.
|
|
|
|
|
|
2012-02-21 08:22:26 +00:00
|
|
|
* QSqlTableModel edit strategies OnFieldChange/OnRowChange QTBUG-2875
|
|
|
|
|
Previously, after changes were submitted in these edit strategies, select()
|
|
|
|
|
was called which removed and inserted all rows. This ruined navigation
|
|
|
|
|
in QTableView. Now, with these edit strategies, there is no implicit select()
|
|
|
|
|
done after committing. This includes deleted rows which remain in
|
|
|
|
|
the model as blank rows until the application calls select(). Instead,
|
|
|
|
|
selectRow() is called to refresh only the affected row.
|
|
|
|
|
|
2012-02-28 21:42:02 +00:00
|
|
|
* QSqlTableModel::isDirty(): New overloaded method to check whether model
|
|
|
|
|
has any changes to submit. QTBUG-3108
|
|
|
|
|
|
QSqlTableModel::setData()/setRecord(): fix incorrect row
For OnFieldChange and OnRowChange, before submitting new changes,
setData() and setRecord() attempt to submit pending changes and
revert them upon failure. However, they fail to consider that
reverting pending insertions removes rows from the model. As a
result, the new change can be applied to a row higher than intended.
One possible solution would be to adjust the targetted index for the
removed rows, so that the intended row is affected by the new change.
But this still causes the strange editing experience as rows jump
up just as they are being edited.
It does not seem right in the first place for the model to initiate
reverting changes. It should be up to the application to decide what
to do when data cannot be committed. In particular, setData() and
setRecord() should not have the side effect of reverting already
pending changes.
The chosen solution is simply to refuse new changes that don't make
sense for the edit strategy. For OnFieldChange, flag() will
indicate read-only when editing is blocked by a pending change.
Since setData() and setRecord() submit data immediately for
OnFieldChange, it no longer makes sense to resubmit changes
automatically before a new change.
For OnRowChange, setData() keeps the behavior of automatically
submitting a pending row before starting on a new row. This is
historical behavior and is probably motivated by the fact that
QTableView does not automatically call submit() when editing leaves a
row. The obvious shortcoming of this is that the last row to be edited
will not be submitted automatically. It also prevents us from flagging
rows other than the pending row as read-only.
For OnRowChange, setRecord(), being row-oriented by nature, should
submit the change immediately rather than waiting for the next call
to setRecord(). This makes setRecord() consistent with insertRecord().
Change-Id: Icb4019d8b7c53a7ee48f8121a7a525e8bc35d523
Reviewed-by: Honglei Zhang <honglei.zhang@nokia.com>
2012-02-28 22:41:31 +00:00
|
|
|
* QSqlTableModel::setData() and setRecord() no longer revert pending changes
|
|
|
|
|
that fail upon resubmitting for edit strategies OnFieldChange and OnRowChange.
|
|
|
|
|
Instead, pending (failed) changes cause new changes inappropriate to the
|
|
|
|
|
edit strategy to be refused. The application should resolve or revert pending
|
2012-02-29 00:51:23 +00:00
|
|
|
changes. insertRows() and insertRecord() also respect the edit strategy.
|
QSqlTableModel::setData()/setRecord(): fix incorrect row
For OnFieldChange and OnRowChange, before submitting new changes,
setData() and setRecord() attempt to submit pending changes and
revert them upon failure. However, they fail to consider that
reverting pending insertions removes rows from the model. As a
result, the new change can be applied to a row higher than intended.
One possible solution would be to adjust the targetted index for the
removed rows, so that the intended row is affected by the new change.
But this still causes the strange editing experience as rows jump
up just as they are being edited.
It does not seem right in the first place for the model to initiate
reverting changes. It should be up to the application to decide what
to do when data cannot be committed. In particular, setData() and
setRecord() should not have the side effect of reverting already
pending changes.
The chosen solution is simply to refuse new changes that don't make
sense for the edit strategy. For OnFieldChange, flag() will
indicate read-only when editing is blocked by a pending change.
Since setData() and setRecord() submit data immediately for
OnFieldChange, it no longer makes sense to resubmit changes
automatically before a new change.
For OnRowChange, setData() keeps the behavior of automatically
submitting a pending row before starting on a new row. This is
historical behavior and is probably motivated by the fact that
QTableView does not automatically call submit() when editing leaves a
row. The obvious shortcoming of this is that the last row to be edited
will not be submitted automatically. It also prevents us from flagging
rows other than the pending row as read-only.
For OnRowChange, setRecord(), being row-oriented by nature, should
submit the change immediately rather than waiting for the next call
to setRecord(). This makes setRecord() consistent with insertRecord().
Change-Id: Icb4019d8b7c53a7ee48f8121a7a525e8bc35d523
Reviewed-by: Honglei Zhang <honglei.zhang@nokia.com>
2012-02-28 22:41:31 +00:00
|
|
|
|
2012-03-13 00:28:35 +00:00
|
|
|
* QSqlTableModel::setData() and setRecord() in OnRowChange no longer have the
|
|
|
|
|
side effect of submitting the cached row when invoked on a different row.
|
2012-03-22 20:27:26 +00:00
|
|
|
|
|
|
|
|
* QSqlDriver::subscribeToNotification, unsubscribeFromNotification,
|
|
|
|
|
subscribedToNotifications, isIdentifierEscaped, and stripDelimiters
|
|
|
|
|
are now virtual. Their xxxImplemenation counterparts have been removed
|
|
|
|
|
now that QSqlDriver subclasses can reimplement these directly.
|
|
|
|
|
|
2011-06-27 14:05:22 +00:00
|
|
|
****************************************************************************
|
|
|
|
|
* Database Drivers *
|
|
|
|
|
****************************************************************************
|
|
|
|
|
|
2012-04-02 20:13:11 +00:00
|
|
|
sqlite
|
|
|
|
|
------
|
|
|
|
|
* QVariant::Bool type now mapped to integers 0/1 in SQL instead of strings
|
|
|
|
|
'true' and 'false'. Sqlite does not have a boolean column type and it is
|
|
|
|
|
customary to use integer. QTBUG-23895
|
2011-06-27 14:05:22 +00:00
|
|
|
|
|
|
|
|
****************************************************************************
|
|
|
|
|
* Platform Specific Changes *
|
|
|
|
|
****************************************************************************
|
|
|
|
|
|
|
|
|
|
Qt for Linux/X11
|
|
|
|
|
----------------
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Qt for Windows
|
|
|
|
|
--------------
|
2011-11-22 13:33:15 +00:00
|
|
|
* Accessibility framework uses IAccessible2
|
2012-05-23 13:07:06 +00:00
|
|
|
* ANGLE can be used to provide Open GL ES 2.0 (see http://code.google.com/p/angleproject/)
|
2011-06-27 14:05:22 +00:00
|
|
|
|
|
|
|
|
Qt for Mac OS X
|
|
|
|
|
---------------
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Qt for Embedded Linux
|
|
|
|
|
---------------------
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Qt for Windows CE
|
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
****************************************************************************
|
|
|
|
|
* Compiler Specific Changes *
|
|
|
|
|
****************************************************************************
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
****************************************************************************
|
|
|
|
|
* Tools *
|
|
|
|
|
****************************************************************************
|
|
|
|
|
|
|
|
|
|
- Build System
|
|
|
|
|
|
2012-01-04 21:21:48 +00:00
|
|
|
* Remove qttest_p4.prf file. From now on we should explicitly enable the
|
|
|
|
|
things from it which we want. Autotest .pro files should stop using
|
|
|
|
|
'load(qttest_p4)' and start using 'CONFIG+=testcase' instead.
|
|
|
|
|
|
2011-06-27 14:05:22 +00:00
|
|
|
- Assistant
|
|
|
|
|
|
|
|
|
|
- Designer
|
2011-12-22 13:51:47 +00:00
|
|
|
* [QTBUG-8926] [QTBUG-20440] Properties of type QStringList now have
|
|
|
|
|
translation attributes which apply to all items.
|
|
|
|
|
They are by default translatable.
|
2011-06-27 14:05:22 +00:00
|
|
|
|
|
|
|
|
- Linguist
|
|
|
|
|
|
|
|
|
|
- rcc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- moc
|
|
|
|
|
|
2011-09-07 16:58:39 +00:00
|
|
|
* [QTBUG-20785] The moc now has a -b<file> option to #include an additional
|
|
|
|
|
file at the beginning of the generated file.
|
|
|
|
|
|
2011-06-27 14:05:22 +00:00
|
|
|
|
|
|
|
|
- uic
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- uic3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- qmake
|
|
|
|
|
|
2011-09-07 16:58:40 +00:00
|
|
|
* QMAKE_MOC_OPTIONS variable is now available for passing additional parameters
|
|
|
|
|
to the moc.
|
|
|
|
|
|
2011-06-27 14:05:22 +00:00
|
|
|
|
|
|
|
|
- configure
|
|
|
|
|
|
2012-05-11 08:03:49 +00:00
|
|
|
* The Mac OS X -dwarf2 configure argument has been removed. DWARF2 is always
|
|
|
|
|
used on Mac OS X now.
|
2011-06-27 14:05:22 +00:00
|
|
|
|
|
|
|
|
- qtconfig
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
****************************************************************************
|
|
|
|
|
* Plugins *
|
|
|
|
|
****************************************************************************
|
2012-01-12 09:43:29 +00:00
|
|
|
- The text codecs that were previously plugins are now built into QtCore.
|
2011-06-27 14:05:22 +00:00
|
|
|
|
|
|
|
|
****************************************************************************
|
|
|
|
|
* Important Behavior Changes *
|
|
|
|
|
****************************************************************************
|
|
|
|
|
|
2011-11-22 13:45:35 +00:00
|
|
|
- QPointer
|
|
|
|
|
|
2012-03-16 23:05:09 +00:00
|
|
|
* The implementation of QPointer has been changed to use QWeakPointer. The
|
|
|
|
|
old guard mechanism has been removed. This causes a slight change
|
|
|
|
|
in behavior when using QPointer:
|
2011-11-22 13:45:35 +00:00
|
|
|
|
|
|
|
|
* When using QPointer on a QWidget (or a subclass of QWidget), previously
|
|
|
|
|
the QPointer would be cleared by the QWidget destructor. Now, the QPointer
|
|
|
|
|
is cleared by the QObject destructor (since this is when QWeakPointers are
|
|
|
|
|
cleared). Any QPointers tracking a widget will NOT be cleared before the
|
|
|
|
|
QWidget destructor destroys the children for the widget being tracked.
|
|
|
|
|
|
2012-04-24 11:33:16 +00:00
|
|
|
- QUrl
|
|
|
|
|
|
|
|
|
|
* QUrl has been changed to operate only on percent-encoded
|
|
|
|
|
forms. Fully-decoded forms, where the percent character stands for itself,
|
|
|
|
|
are no longer possible. For that reason, the getters and setters with
|
|
|
|
|
"encoded" in the name are deprecated, except for QUrl::toEncoded() and
|
|
|
|
|
QUrl::fromEncoded().
|
|
|
|
|
|
|
|
|
|
QUrl now operates in a mode where it decodes as much as it can of the
|
|
|
|
|
percent-encoding sequences. In addition, the setter methods possess a mode
|
|
|
|
|
in which a '%' character not part of a percent-encoding sequence will cause
|
|
|
|
|
the parser to correct the input. Therefore, most software will not require
|
|
|
|
|
changes to adapt, since the getter methods will continue returning the
|
|
|
|
|
components in their most-decoded form as they did before and the setter
|
|
|
|
|
methods will accept input as they did before..
|
|
|
|
|
|
|
|
|
|
The most notable difference is when dealing with
|
|
|
|
|
QUrl::toString(). Previously, this function would return percent characters
|
|
|
|
|
in the URL by themselves. Now, it will return "%25", like
|
|
|
|
|
QUrl::toEncoded().
|
2012-01-07 07:23:17 +00:00
|
|
|
|
2012-01-30 11:21:43 +00:00
|
|
|
- QVariant
|
|
|
|
|
|
|
|
|
|
* Definition of QVariant::UserType changed. Currently it is the same as
|
|
|
|
|
QMetaType::User, which means that it points to the first registered custom
|
|
|
|
|
type, instead of a nonexistent type.
|
|
|
|
|
|
2012-02-13 15:26:35 +00:00
|
|
|
- QMetaType
|
|
|
|
|
|
|
|
|
|
* Interpretation of QMetaType::Void was changed. Before, in some cases
|
|
|
|
|
it was returned as an invalid type id, but sometimes it was used as a valid
|
|
|
|
|
type (C++ "void"). In Qt5, new QMetaType::UnknownType was introduced to
|
|
|
|
|
distinguish between these two. QMetaType::UnknownType is an invalid type id
|
|
|
|
|
signaling that a type is unknown to QMetaType, and QMetaType::Void
|
|
|
|
|
is a valid type id of C++ void type. The difference will be visible for
|
|
|
|
|
example in call to QMetaType::typeName(), this function will return null for
|
|
|
|
|
QMetaType::UnknownType and a pointer to "void" string for
|
|
|
|
|
QMetaType::Void.
|
|
|
|
|
Please, notice that QMetaType::UnknownType has value 0, which previously was
|
|
|
|
|
reserved for QMetaType::Void.
|
|
|
|
|
|
2012-01-30 11:21:43 +00:00
|
|
|
|
2012-01-07 07:23:17 +00:00
|
|
|
- QMessageBox
|
|
|
|
|
|
|
|
|
|
* The static function QMessageBox::question has changed the default argument
|
|
|
|
|
for buttons. Before the default was to have an Ok button. That is changed
|
|
|
|
|
to having a yes and a no button.
|
