| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
These compilers compile this code fine, but this warning shows up
*everywhere* when building Qt (or used to, since qstringlist.h
included qstringmatcher.h).
Move the structure definition to outside the union.
|
| |
|
|
|
|
|
| |
Don't use easing too much. Also add an explanation of what "ease in"
and "ease out" is.
|
|
|
|
|
|
|
|
|
|
|
| |
* Remove some references to QAnimation. QAnimation does not exist.
* Clarify the documentation for QEasingCurve::Linear. (avoid "tweening"
and "no easing")
* In the diagrams, change "ease" to "value".
* Change the diagram generation code to use antialiased drawing
(just as we do in the easingcurve example)
Reviewed-by: leo
|
|
|
|
|
| |
Task-number: related to 253013
Reviewed-by: João Abecasis
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/3rdparty/webkit/WebCore/generated/JSDOMWindow.cpp
src/3rdparty/webkit/WebCore/page/DOMWindow.idl
src/corelib/io/qdiriterator.cpp
src/plugins/gfxdrivers/directfb/qdirectfbpaintengine.cpp
src/plugins/gfxdrivers/directfb/qdirectfbpixmap.h
tests/auto/qxmlquery/tst_qxmlquery.cpp
tools/linguist/lconvert/main.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
during application desctruction globalEngineCache is deleted as part
of Q_GLOBAL_STATIC macro. Other instances of code that happen to use
QRegex after the cache destruction will subsequently crash. Most common
reason are other Q_GLOBAL_STATIC instances which happen to use QRegExp
as part of their destructor.
Reviewed-by: Rhys Weatherley
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Better usage of move semantics with implicit sharing to avoid
detaching (=malloc/memcpy). Also some other improvements.
Download performance improvement is around 20% according
to the httpDownloadPerformance autotest.
Reviewed-by: Thiago Macieira
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
with qstring.
The qstring unicode conversion functions used to have its own
implementation, which did the same as QUtf*Codecs, so with the change
all of them will share the same implementation.
Reviewed-by: Thiago Macieira
|
| | |
|
|\ \ |
|
| | | |
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | | |
we should include qt_windows.h and not windows.h because we have to
define WINVER to 0x500.
|
| | |
| | |
| | |
| | | |
Reviewed-by: Volker Hilsheimer
|
| | | |
|
| | |
| | |
| | |
| | | |
It tries to keep the semantics of QString::append(QByteArray) as much as possible.
|
| | |
| | |
| | |
| | | |
make compiler distinguishing both happy.
|
| | | |
|
| | | |
|
|\ \ \
| |/ / |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QSharedPointer"
This reverts commit fb51a10ee0451274a430227566ae26efb2ac4474.
Sorry, it didn't work. I can fix the MSVC error, but the problem is
that older GCC versions (4.2) fail with the following code:
template<typename T> struct Buffer
{
char buffer[128] __attribute__((aligned(__alignof__(T))));
};
The same works fine in GCC 4.4.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
are declared in this file.
The one-definition rule allows the forward declaration appearing below to
apply to code that was earlier. Therefore, if the compiler finds out
how to delete the object, we can allow a QSharedPointer of a forward-
declared-type.
This means the actual problem is just a warning with g++. To catch the
error, we need a separate .cpp file and I'd rather run this as an
external test.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
one go.
This avoids one memory allocation. Currently, we only support calling
the default constructors. I will *NOT* implement argument passing for
C++03. I will implement it with rvalue references for C++0x-capable
compilers.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This obviously only works for classes that derive from QObject. And
you must remember that QSharedPointer controls the QObject's lifetime,
not the QObject parent-child relationship.
Reviewed-by: dt
Reviewed-by: Bradley T. Hughes
|
| |\ \
| | |/ |
|
| | |
| | |
| | |
| | | |
Reviewed-by: trustme
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is related to the following fix:
70137e0601549af1056082cdfbb4f141c70befab
Reviewed-by: trustme
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Directly put a QRingBuffer from one QRingBuffer to
another QRingBuffer.
Reviewed-by: Thiago Macieira
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
support
Also: QString::fromUtf16() -> QString::fromWCharArray()
WCHAR & TCHAR -> wchar_t
LPTSTR/LPCTSTR -> LPWSTR/LPCWSTR
Documentation update
Merge-request: 604
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In QTime::currentTime(), the pointer to the tm structure was used
without being initialized.
Task-number: 256889
Reviewed-by: Markus Goetz
|
| | |
| | |
| | |
| | |
| | | |
These four enum values are used in variables of type Section, but aren't in it.
With gcc 4.4, it displays a warning that the value is lower than the lowest value
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There's no need to have separate cast-checker functions, plus the cast-
and centralise the function to create the object.
Reviewed-by: TrustMe
|
| |\ \
| | |/
| | |
| | |
| | |
| | | |
Conflicts:
src/plugins/gfxdrivers/directfb/qdirectfbpaintengine.cpp
src/plugins/gfxdrivers/directfb/qdirectfbpixmap.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
enabled.
This allows mixing of debug and non-debug code (possible on Unix
systems) without causing assertion failures.
Reviewed-by: Bradley T. Hughes <bradley.hughes@nokia.com>
|
| |\ \
| | |/
| | |
| | |
| | | |
Conflicts:
tests/auto/qsqldatabase/tst_databases.h
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Two strings are only equal if they have the same size.
Task-number: 256763
Reviewed-by: TrustMe
|
| | |
| | |
| | |
| | |
| | |
| | | |
Removed lots of places where we check for Tiger. Now we can assume it.
Reviewed-by: Morten Sørvig
|
| |\ \
| | |/
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/3rdparty/webkit/VERSION
src/3rdparty/webkit/WebCore/ChangeLog
src/3rdparty/webkit/WebKit/qt/ChangeLog
tests/auto/qgraphicsitem/tst_qgraphicsitem.cpp
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In 4.4 QRectF handled flat rectangles in the same fashion as QRect does,
but that changed with Lars' and Jo's optmizations done in the falcon
branch. The difference is that the optimized version only checks whether
the width or height is 0, whereas in 4.4 both had to be 0 (isNull()) before
we bailed out.
This regression also introduced a regression in
QGraphicsItem::childrenBoundingRect().
Auto-test included.
Task-number: 254995
Reviewed-by: Lars
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
enum Qt::Uninitialized contains one value, which is also called
Uninitialized. Because the type and the value used the same name,
wherever the type Qt::Uninitialized was used in a function signature,
you had to include the enum keyword. But qdoc's preprocessor doesn't
like that, so you have to take the enum keyword out of the signatures.
But then the compiler complains because the type and the value look
the same. So I had to change the enum type name to Initialization, so
the compiler can distinguish it from the value name. And qdoc likes
that too.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Directly construct uninitialized QByteArrays of required size
instead of default-constructing one and resizing it afterwards.
Reviewed-by: mariusSO
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Contrary to the QByteArray::QByteArray(int size, enum Qt::Uninitialized)
constructor this does not initialize its data.
Reviewed-by: mariusSO
|