| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
We already convert date/time format inside the getMacDateFormat, so no reason
to do it again later.
Reviewed-by: Prasanth
|
| |
| |
| |
| |
| |
| | |
Revert a change that is not yet complete and was pushed by mistake.
This reverts commit 44f7c1e097582a704a06ccbbf516536b88ddcd3a.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Subscribing to the locale change notification to be able to update the
system locale whenever the user changes the current system locale.
Also changed the initialization of the system locale to make construction of
the QLocale object as lightweight as possible. So now the default contructor
just creates a QLocale and QSystemLocale objects, but doesn't try to fill the
cache in the latter with data from the system and postpones it until it is
actually requested (most applications create QLocale objects on the stack and
might not even use the data from the system locale, so we don't need to
initialize system locale right away).
Modified-by: axis
Modified-by: Denis Dzyubenko
Reviewed-by: Denis Dzyubenko
Reviewed-by: axis
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
src/s60installs/bwins/QtGuiu.def
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
qcache.h:73: warning: declaration of 'object' shadows a member of this
Spotted by compilerwarnings autotest
Reviewed-by: Thiago
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We need to store a pointer to the object in order to delete it later,
since the node containing the pointer will be deleted when removing it
from the hash.
Reviewed-by: Jan-Arve Sæther
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Removing a pixmap from the pixmap cache using the new QPixmapCache::Key
API left the keys dangling in the QCache's internal QHash. The problem
is that the Key is invalidated as soon as the QPixmapCacheEntry is
destroyed, thus removing it from the hash failed. Reordering the
destruction of the object and the removal of the key in QHash fixes the
problem.
Reviewed-by: Alexis
Reviewed-by: Thiago
|
| |/
| |
| |
| |
| |
| |
| | |
uses of QT_DEPRECATED must be protected by #ifdef
Task-number: QTBUG-6649
Reviewed-by: João Abecasis
|
|/
|
|
|
|
|
|
|
|
|
|
| |
In some places we do have direct math related calls. Almost all are
calling the double precision functions even if the args and results
are float.
This leads to unnecessary float->double and double->float transitions.
By using wrapper functions we can control which functrion variants
are effectively called.
Task-number: QTBUG-4894
Reviewed-by: Shane Kearns
|
|
|
|
|
|
|
|
| |
Use qFuzzyCompare instead of an exact floating point comparison when
checking if valueChanged should be emitted.
Task-number: QTBUG-6189
Reviewed-by: Dmytro Poplavskiy
|
|\
| |
| |
| | |
oslo-staging-1/4.6 into 4.6
|
| |
| |
| |
| |
| |
| |
| |
| | |
When you cast from a 64-bit type to a 32-bit one, MSVC produces an
RTCF, despite the explicit cast. The solution is to add & 0xFFFFFFFF.
Task-number: QTBUG-4255
Reviewed-by: Marius Storm-Olsen
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We cannot call realloc with aalloc smaller than asize.
Also include obvious optimisation: take the qMin computation out of
the loop.
Task-number: QTBUG-6416
Reviewed-by: Thiago
|
|/
|
|
| |
Reviewed-by: Harald Fernengel
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Someone had changed an operator==() and an operator!=() from
single parameter members to two-parameter friends but hadn't
changed the qdoc comments.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add the "reserved" member to QVectorData in that configuration. Since
this is only about the bootstrapped version of Qt, there are no binary
compatibility issues.
Reviewed-by: Bradley T. Hughes
|
| |
| |
| |
| |
| |
| | |
Someone had changed an operator==() and an operator!=() from
single parameter members to two-parameter friends but hadn't
changed the qdoc comments.
|
| |
| |
| |
| |
| | |
for some reason, this did build on linux and windows, but symbian seems
somewhat stricter.
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The API is internal, so it should live in its private header. The class
was introduced during the lifetime of 4.6 (not in 4.5), so the move is
binary compatible.
Task-number: QTBUG-5617
Reviewed-by: João Abecasis <joao@abecasis.name>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Non-member operator allows implicit conversions on both arguments.
A single operator is enough to support QScopedArrayPointer,
QCustomScopedPointer and QScopedSharedPointer since equality semantics
don't change and the deleter is managed in the base class.
Reviewed-by: Marius Storm-Olsen
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
tools/configure/configureapp.cpp
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/corelib/tools/qscopedpointer.h
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Non-member operator allows implicit conversions on both arguments.
A single operator is enough to support QScopedArrayPointer,
QCustomScopedPointer and QScopedSharedPointer since equality semantics
don't change and the deleter is managed in the base class.
Reviewed-by: Marius Storm-Olsen
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
QRegExp::numCaptures() is marked as obsolete.
Replaced all usage in Qt and test-cases.
Reviewed-by: Andreas Aardal Hanssen
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
needed for build-time qm generation in qt itself.
the downsides are a) that the other bootstrapped tools grow by ~12kB
(on x86) due to qdatastream being pulled in by qbytearray and qstring
and b) that lrelease isn't l10n'd itself anymore (the latter could be
fixed by building a non-qobject qtranslator).
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
The API is internal, so it should live in its private header. The class
was introduced during the lifetime of 4.6 (not in 4.5), so the move is
binary compatible.
Task-number: QTBUG-5617
Reviewed-by: João Abecasis <joao@abecasis.name>
|
|\ \ |
|
| |\ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
dist/changes-4.6.0
|
| | |\ \
| | | |/
| | |/| |
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: Iain
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Enables N'Ko support in Qt, after having now a harfbuzz version
that supports it.
Task-number: QTBUG-1042
Reviewed-by: Gunnar
|
| |/ |
|
| |
| |
| |
| |
| |
| | |
prevents leaking the pragma out of the header file
Task-number: QT-2267
|
| |
| |
| |
| |
| | |
Forward declare struct QAbstractConcatenable correctly.
Reviewed-by: hjk <qtc-committer@nokia.com>
|
|\ \
| |/ |
|
| |\ |
|
| | |
| | |
| | |
| | | |
Reviewed-by: TrustMe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is future compatibility: we must rely on them being 0 in older
versions of Qt.
Reviewed-by: Bradley T. Hughes
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QContiguousCache is a new type, so there are no binary compatibility
issues.
QHash and QMap didn't have any public qMalloc / qFree, so the entire
logic is contained in .cpp code. However, since old code will not
inform us of the alignment requirements, we need to add a bit to the
structure to indicate whether strict alignment is in use or not.
QList doesn't require any changes. For small, movable types, they're
all stored in the pointer array itself, so they're aligned. For larger
types, we use new(), so types with stricter requirements should define
their own operator new().
QLinkedList cannot be fixed. It uses new() on the QLinkedListNode,
which contains a T type. Sorry.
QVector did have public qMalloc / qFree. I've moved the calls to the
inner function and made it keep the old calls if the alignment
requirement is below a certain threshold. The idea is that, if it's
above, no one was using QVector anyway.
Reviewed-by: Bradley T. Hughes
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The private inheritance ensures that we don't try to access the types
under the wrong pointer. If we did that, we'd cause strict aliasing
violations.
Reviewed-by: Olivier Goffart
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Now, it's a real drop-in replacement, with no known feature regressions
:)
Reviewed-By: hjk
|
|/ /
| |
| |
| |
| |
| |
| | |
the indexOf() call did not consider actualReadBufferSize and thus
scanned uninitialized memory for newlines.
Reviewed-by: phartman
|
|\ \ |
|
| |/
| |
| |
| | |
Reviewed-by: Denis Dzyubenko
|
|\ \ |
|