| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Reviewed-by: trustMe
|
|
|
|
|
|
|
|
|
| |
added new method QNetworkAccessManager::deleteResource (naming the
method "delete" was not possible since it is a reserverd word in
C++) and adjusted all the internals necessary.
Task-number: 242916
Reviewed-by: Thiago
|
|
|
|
| |
Reviewed-by: Joerg
|
|
|
|
|
|
|
|
|
|
|
| |
The check for cleartype in qt_win_read_cleartype_settings() was not
correct for Windows Mobile
For anti-aliased text rendering we also have to use another
pixel format for the native image.
Task-number: 249642
Reviewed-by: mauricek
|
| |
|
|
|
|
|
|
|
|
|
| |
We've had a problem with a stale cache for color profiles this should
make things work well. We get the callback for each display whether it
needs it or not, but honesly I would rather that we update this a few
times too many when people change their display profile than not at all.
FWIW, this code is inspired from Apple's Tech Note TN2035.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
What could happen starting with 4.4 is that you could move a toolbar.
If you then added actions, the toolbar would grom and make the other
toolbars move to the right although it had enough space already to show
the newly created actions.
Autotest will follow shortly.
Task-number: 226060
|
|
|
|
|
|
|
|
| |
So far, only operator% was working for concatenation in those circumnstances.
Now, defining QT_USE_FAST_OPERATOR_PLUS and QT_USE_FAST_CONCATENATION is
enough, so user code will work without any source changes.
Reviewed-by: joao
|
|
|
|
|
| |
Merge-request: 384
Reviewed-by: Marius Storm-Olsen <marius@trolltech.com>
|
|
|
|
|
|
|
|
| |
An alternative solution is to swap the order of
-I../../include and -I../../include/QtOpenGL when
compiling the opengl module.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
| |
As checked in was compiling with QDataStream(QByteArray *, int) and
that method is only available when compiling with qt3 support.
Reviewed-by: Julian de Bhal
|
|
|
|
|
|
|
| |
seem fixable easily)
Merge-request: 594
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
|
|
|
|
|
| |
Merge-request: 594
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Whenever an argument failed to marshall, this assert would be
triggered. It's technically an error in the application, but it's hard
to track it down. So remove it and let the execution continue (the
function returns false indicating failure already and there's a
warning from the marshalling code itself)
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| | |
This patch prevents the eventloop from waking up needlessly.
Without this patch the event loop will not sleep at all if a 0-timer is already 'inTimerEvent'
Merge-request: 550
Reviewed-by: Olivier Goffart <ogoffart@trolltech.com>
|
| |
| |
| |
| |
| |
| | |
We were saying that it connected to accepted it all these cases, but it
actually is doing some nice magic that makes sense assuming you document
it.
|
| |
| |
| |
| |
| |
| |
| |
| | |
No progress bars on the mac show text and it would be bad if we allowed
it. There's nothing stopping people from connecting the valueChanged()
signal to a slot and have a real label layed out correctly that actually
updates with the amount of time it takes to complete, etc. This is more
what they do on Mac OS X if they decide to show a label.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
QMotifStyle
Same fix as in e9a7e43031d7c1ee712e43be682c4e2c183759c4 but with motif
Reported by https://bugs.kde.org/show_bug.cgi?id=193911
Task-number: 255138
Reviewed-by: jbache
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was quite a bug and it showed to some issues that I hadn't taken
into account when doing the initial port to Cocoa. The issue was that we
weren't "merging" items into the application menu if an item had already
been associated with it. Which seems OK for applications that create one
window with one menubar, but breaks down horrible when you have multiple
windows with each having their own menubar. The result is that items in
the application menu potentially go to the wrong window (and the
potential crash). Since there can only ever be one "Quit", "About", or
"Preferences" menu item in Cocoa, we need to make sure that we keep
these items in sync whenever we switch the menubar or remove actions
that are being deleted. That's what we do here.
FWIW, QActions with "ApplicationSpecificRole" for their menu role have
potential to cause memory leaks or other bugs if abused. If you are a
happy open source hacker who wants a thankless job, solving them would
get you lots of goodwill in my book.
Task-number: 255038
Reviewed-by: Richard Moe Gustavsen
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The blend functions assume the width / height of the images being
blended to be greater than 0. A width of 0 caused the first iteration of
a duff's device memcpy (QT_MEMCPY_USHORT) to be executed, thus blending
8 pixels instead of none.
BT: yes
Task-number: 255014
Reviewed-by: Trond
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The BOM was created correctly, but half of the BOM was then overwritten
by the converted data afterwards.
Also made the autotest also do reverse encoding tests where possible.
Task-number: 255095
Reviewed-by: lars
|
| |
| |
| |
| |
| |
| | |
otherwise PeekNamedPipe() may block in threaded environments.
Reviewed-by: thiago
|
| |
| |
| |
| | |
Reviewed-by: Kavindra Palaraja
|
| |
| |
| |
| |
| |
| |
| |
| | |
The R and B channels were swapped on little endian machines with
BGR layout.
Task-number: 254934
Reviewed-by: Samuel
|
| | |
|
| |
| |
| |
| | |
Reviewed-by: Thierry Bastian
|
| |
| |
| |
| | |
There should be no QT_{BEGIN,END}_HEADER here; this is a private header.
|
| |
| |
| |
| |
| |
| |
| | |
All Qt headers must have QT_BEGIN_HEADER, QT_END_HEADER and
QT_MODULE. These headers didn't have this.
Reviewed-by: TrustMe
|
| |
| |
| |
| | |
includes)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
HITheme doesn't seem to support the reverse thing. I filled a bug about
it, but this is easy to emulate in the horizontal case and the
"Inverted" orientation works great for vertical.
Task-number: 217594
Reviewed-by: Morten Sørvig
|
| |
| |
| |
| | |
Reviewed-by: TrustMe
|
| |
| |
| |
| | |
Reviewed-by:David Boddie
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
In the style code, the internal UsePixmapCache flag made
no sense in practice, so it was removed. A fortunate side-effect
of the patch is that the code is now accepted by Sun CC 5.5.
Reviewed-by: jbache
|
| |
| |
| |
| | |
Reviewed-by: tbastian
|
| |
| |
| |
| |
| |
| |
| |
| | |
Note that the fix is simply to swap the order of the
two v_construct() overloads. Sun CC 5.5 requires the
version with the default argument to occur first.
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| |
| | |
a QStatusBar
Task-number: 253717
Reviewed-by: ogoffart
|
| |
| |
| |
| | |
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| | |
Task-number: QT-80
Reviewed-by: Ian Walters
|
| |
| |
| |
| |
| | |
Task-number: QT-80
Reviewed-by: Ian Walters
|
| | |
|
| |
| |
| |
| |
| | |
These function exist for making code not look so crazy, so let's
actually use that in code where it didn't exist before.
|
| |
| |
| |
| |
| |
| |
| | |
but the current highlighted item doesn't change
Task-number: 254238
Reviewed-by: ogoffart
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Yeesh.
The function worked for the common case of the argument being a plain
script object (obviously, otherwise this would have been discovered
sooner), but it would never pick the less expensive path when replacing
the QObject pointer of an existing proxy. And if you passed in a
QVariant proxy (now who would ever do something like that...?),
it would assert.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When pressing the <- key on a Windows mobile device, the window gets
a minimized event (no other soft keys behave like that). Restoring the
window via the app menu isn't possible, because the window get a
WM_ACTIVATE but its internal state is still minimized.
It makes sense to unminimize activated apps on Windows mobile.
Task-number: 254673
Reviewed-by: thartman
|
| |
| |
| |
| |
| | |
The signal code (first character of const char *signal) is stripped
internally, so the debug output code should not skip any characters.
|