| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Lots of warnings in the qreal == float case.
Some Q_UNUSED added.
Reviewed-by: thartman
|
|
|
|
|
|
| |
These might work with the new JavaScriptCore-based back-end.
Will re-add any expected failures once the autotest results are in
from the platforms tested on Pulse.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't crash when parsing
"<?xml version=\"1.0\" encoding=\"iso-8859-1\" ?><guid><http://www.foo.dk/artikel/8938</guid>"
(unmatched "< tag followed by "foo:") using QDomDocument::setContent
together with a QXmlSimpleReader with the
"http://xml.org/sax/features/namespaces" feature enabled.
Fixes task tracker issue 254700. See there for a test case.
Merge-request: 1322
Reviewed-by: Peter Hartmann <peter.hartmann@trolltech.com>
|
|
|
|
|
|
|
|
|
| |
All of the types supplied to qBound() must be the same and in the case
where qreal is typedef'ed to a float, this is not the case because the
outer 2 arguments are considered doubles. We explicitly cast them to
qreal to guarantee they are all the same type.
Reviewed-by: bnilsen
|
|
|
|
|
|
|
| |
Add "requires(symbian)" to the .pro file so this test will not be
executed on other platforms.
Reviewed-by: Rohan McGovern
|
|
|
|
|
|
|
| |
Auto-test submitted.
Task-number: 259503
Reviewed-by: bnilsen
|
|
|
|
| |
Reviewed-by: hjk
|
|
|
|
|
|
|
|
|
|
| |
QVectorPath::hints() is not a strict bit field, and thus can not be
anded with RectangleHint. Instead, QVectorPath::shape() should be
directly compared with RectangleHint to check if the vector path is a
rectangle or not. In this case the first four points of a regular
painter path were treated as a rectangle with dire consequences.
Reviewed-by: Tom
|
|
|
|
|
|
|
| |
We now need to connect to the slot in the QLineControl and not to the
slot of the QLineEdit (the QLineEdit slot is now also removed).
Reviewed-by: Alan Alpert
|
|
|
|
| |
13 pairs missing...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Why this happends is a bit blurry. From before, I know that
cocoa is a bit buggy regarding setting a menu item
hidden or not. The solution back then resulted in the function
syncNSMenuItemEnabled in qmenu_mac.mm. This patch basically
applies the same (silly) trick; disabling the menuitem before
enabling it. This seems to force an update to the menu items
enabled state. For the record: this is not a fix that I
embrace. I hope we can remove it again some day. See
task for how to reproduce.
Task: 259600
Rev-By: alexis
|
|
|
|
|
|
|
|
| |
Had left the cursor flash time as half the QApplication cursor flash
time by mistake. The new function sets the whole period and not just the
time between toggling cursor visibility.
Reviewed-by: Trust Me
|
|
|
|
|
|
|
| |
To prevent using IDirectFBImageProviders one can define
QT_NO_DIRECTFB_IMAGEPROVIDER
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
| |
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
|
|
|
| |
Some DFB implementations do not support rendering the cursor using the
intended interfaces. In these cases one can define
QT_DIRECTFB_WINDOW_AS_CURSOR and use a window to render the cursor.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
| |
If you define QT_DIRECTFB_IMAGEPROVIDER_KEEPALIVE we make sure atleast
one IDirectFBImageProvider is alive at all times.
Apparently this is refcounted by DirectFB on atleast one implementation
and there's considerable overhead involved when releasing the
last/creating the first image provider.
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
| |
Reimplement QPixmapData::fromFile/fromData to load images using
IDirectFBImage providers. This functionality might be accelerated on
embedded boards and could have potentially large performance
enhancements.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
|
|
| |
If we actually need it locked we'll probably need it locked for
read|write.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
|
|
| |
Move format into QDirectFBPaintDevice.
Reviewed-by: Donald Carr <donald.carr@nokia.com>
|
|
|
|
| |
Reviewed-By: TrustMe
|
|
|
|
| |
Reviewed-By: TrustMe
|
|
|
|
|
|
|
|
| |
The problem was that the mode was not emitting dataChanged.
Note: This still needs to be autotested.
Task-number: 234641
Reviewed-by: ogoffart
|
|
|
|
| |
Also include some spaces fix
|
|
|
|
|
|
| |
This will remove a false pmemleak under valgrind.
Reviewed-by: ogoffart
|
|
|
|
|
|
|
| |
The entry point has been changed to be customShader, taking source
image and texture coordinates as parameters.
Reviewed-by: Tom
|
|
|
|
| |
Reviewed-by: Tom
|
|
|
|
|
|
|
|
| |
QRectF::intersects was optimized as part of the Falcon project, and is
now a bit faster than the inline version used here (drawing of dashed
lines was measured to take 16% less time).
Reviewed-by: Lars Knoll <lars.knoll@nokia.com>
|
|
|
|
|
|
|
|
| |
The problem was we were iterating over the list of running animations.
And when calling setCurrentTime(<duration>) on one of them they just
unregister themselves from the timer and we would miss some of them.
Reviewed-by: leo
|
|
|
|
| |
Reviewed-by: Thierry
|
|
|
|
|
|
|
|
|
|
| |
Especially when the widget was not yet shown. Sometimes the rectangle
for an item would get truncated to the size of the viewport.
That should not happen: we only want to expand it to take the whole
height or width of the viewport.
Task-number: 243335
Reviewed-by: ogoffart
|
|\ |
|
| |
| |
| |
| |
| |
| | |
We must not forget to delete the control
Reviewed-by: Paul
|
|/ |
|
|
|
|
| |
QPoint -> QPointF
|
|
|
|
|
|
| |
We export one extra private symbol from QtCore instead, and use that.
RevBy: Miikka Heikkinen
|
|
|
|
|
|
| |
Fix the eyes border in plasma
Author: Kim
|
|
|
|
|
| |
Adding a second patch to this problem. This patch hooks into an
earlier stage in the 'use native' detection
|
|
|
|
| |
Task-number: 259331
|
|
|
|
| |
Author: Kim
|
|
|
|
|
| |
Task-number: 260134
Reviewed-by: ogoffart
|
|
|
|
|
|
|
| |
The bug this commit fixes was introduced by commit
28ac217b04abaa4d226e43e402c14a88539fca3b.
Reviewed-by: Trond
|
|
|
|
|
|
| |
Some minor harmless fixes after feedback from code review.
Reviewed-by: Espen Riskedal
|
|
|
|
|
|
|
|
|
|
|
| |
It seems like we don't respect the Qt::AA_MacPluginApplication
attribute. Setting this attribute means that the native application
should control the menu bar. This patch does a check for this, and
leaves the menubar alone if its set.
We could consider allowing menubars if the Qt::AA_DontUseNativeMenuBar
is set (those should placed inside the window)
Reviewed-by: msorvig
|
|
|
|
|
|
|
| |
Seems like the QMacNativeWidget was almost not
testet at all. It all breaks down when embedding
QLineEdits (with respect to focus). This is a
first patch that fixes this issue.
|
|
|
|
| |
Some compilers don't like them and fail to compile.
|
|
|
|
|
|
|
|
| |
QScriptValuePrivate released by garbage collector later in
~QScriptEnginePrivate (when destroying the agents) would be
added to the freelist and not be released
Reviewed-by: Kent Hansen
|
|
|
|
| |
Reviewed-by: Kent Hansen
|
|\ |
|
| |
| |
| |
| | |
Reviewed-by: Jason Barron
|