| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Task-number: QTBUG-7480
Reviewed-by: Trust Me
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
| |
Task-number: QTBUG-7606
(cherry picked from commit 634eac05a6475280f2a1cc6e41e23c0c35628247)
|
|
|
|
|
|
|
| |
Bug was introduced by af30aeb6a1ebb7307f06c122c0c93d152f4d958c
Contributed-by: Ritt Konstantin
(cherry picked from commit cefda8e4491ff82c96fceea2091f69160f8ae584)
|
|
|
|
|
|
|
|
|
|
| |
This avoids a number of reallocations due to appending.
This patch was contributed to us.
Task-number: QTBUG-3242
Reviewed-by: Thiago Macieira
(cherry picked from commit 7461ed5227e3002c4a6f74d458aa0255b7c1217d)
|
|
|
|
|
|
|
|
| |
audio-backend option was not being written out to qconfig.pri
Task-number:QTBUG-7782
Reviewed-by:Justin McPherson
(cherry picked from commit 65493e69454f8914d0ae1607e5a071ea07bb7017)
|
|
|
|
|
| |
Reviewed-by: Sarah Smith
(cherry picked from commit 416cf8a5a9384f942282a2c715ec4832eeba001d)
|
|
|
|
|
|
|
|
|
|
| |
The removed code simply reduces the size of the rect when running
with RightToLeft without compensating anywhere else. It seems to be
a leftover from a previously removed piece of code.
Reviewed-by: richard
Task-number: QTBUG-6882
(cherry picked from commit b4d60000981e298b7e40605a284f2b8b9b18fff5)
|
|
|
|
|
|
|
|
|
|
|
| |
Regression was introduced by commit
fd9cdaa55da455b90eacec571aeb2c84fa55f7e0.
Also fix a completely broken autotest that didn't actually test
anything.
Task-number: QTBUG-7688
Reviewed-by: Alexis
(cherry picked from commit 0585997b7dbe25ece9f60684171c16206d10d65f)
|
|
|
|
|
| |
Task-number: QTBUG-7640
(cherry picked from commit aebc34877fb17405e8e5915760012a82d0178b97)
|
|
|
|
|
| |
Task-number: QTBUG-7628
(cherry picked from commit a2c153f01c9b12eb6f1d46ffaf5533bb7b3695e2)
|
|
|
|
|
| |
Task-number: QTBUG-7626
(cherry picked from commit fc7b48c2d2fb5926fa0b50f378fadc583564b7b8)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
menu hiding.
The problem here was the way we entered Full Screen Mode. We were using
"kUIModeAllSuppressed" which does the following according to the manual:
kUIModeAllSuppressed
All system UI elements (including the menu bar) are hidden. However,
these elements may automatically show themselves in response to mouse
movements or other user activity.
I changed it to "kUIModeAllHidden", which does the following:
All system UI elements (including the menu bar) are hidden.
To prevent a change of behavior I added the following option to the
SetSystemUIMode:
kUIOptionAutoShowMenuBar
This flag specifies that the menu bar automatically shows itself when
the user moves the mouse into the screen area that would ordinarily be
occupied by the menu bar.
Only valid for the presentation mode kUIModeAllHidden.
Task-number: QTBUG-7625
Reviewed-by: Richard Moe Gustavsen
(cherry picked from commit 9d207f042ea135eda6bcd91c47d581914470fa6d)
|
|
|
|
|
| |
Task-number: QTBUG-7605
(cherry picked from commit aa854adabedbe5ff95d02c0371ae90d85921061c)
|
|
|
|
|
|
|
|
|
| |
If you use refs, then you can't use this operator as the first
argument, since qDebug() returns QDebug by-value (an rvalue
temporary). That cannot be bound to a non-const ref.
Task-number: QTBUG-7593
(cherry picked from commit 0c822ea63a8b2b0c32c68a49de81e0c02548f059)
|
|
|
|
|
|
| |
Task-number: QTBUG-7549
Reviewed-By: Markus Goetz
(cherry picked from commit 206fffb5927bae05a8d8b81c810c33a1c7a70a69)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The problem here is the fact that we "trusted" the user when the widget
type was specified. The fix consists in checking the result of the
conversions, if the conversion was successful (i.e. the widget was of
the type specified by the user) then we proceed as usual. If the
conversion was not successful (i.e. wrong widget type) then we ask the
style for a sensible size.
I modified this for QPushButton, QSlider and QToolButton.
Task-number: qtbug-7522
Reviewed-by: jbache
(cherry picked from commit f92e9c32160ca32b93173dafad2734963528446d)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the user provided their own shader with glShaderBinary(),
QGLShaderProgram::addShader() would refuse to add it because
it wasn't marked as "compiled". According to the OpenGL/ES 2.0
specification:
"It is permissible to attach a shader object to a
program object before source code has been loaded into the
shader object or before the shader object has been compiled."
Based on this, the compile check has been removed from addShader()
which should make supporting binary shaders easier.
Similarly, link() and programId() have been modified to support
applications that use glProgramBinaryOES() to specify program binaries.
Task-number: QTBUG-7490
Reviewed-by: Tom Cooksey
(cherry picked from commit 6b6b206ed8634323570712e003fc159fbf5f8303)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The problem is that we didn't check if the event dispatcher was
interrupted before starting to wait for more events. This patch will do
the interrupt test after processing modal session events, and just
before starting to wait. This will fix applications that expects e.g an
event loop to exit immidiatly upon a signal from a timer (without the
need for the user to generate e.g. a mouse event to stop the wait).
Task-number: QTBUG-7503
Reviewed-by: cduclos
(cherry picked from commit 8cdab74082019c0b8a57883a11aa5093a644abdd)
|
|
|
|
|
|
|
| |
Task-number: QTBUG-7316
Task-number: QTBUG-7317
Reviewed-by: thiago
(cherry picked from commit ef89c6a9f39924a3c8366ad9522b42e7b1915b01)
|
|
|
|
|
|
|
|
|
|
|
| |
The crash happens while processing a paint message received by the
NSToolbar after the corresponding QToolbar has been destroyed. So while
cleaning up the toolbar, the view needs to be detached from the custom
toolbar item.
Task-number: QTBUG-7305
Reviewed-by: Carlos Manuel Duclos Vergara
(cherry picked from commit c56ede1d6f5082cd10c310d473779cfea3363fe6)
|
|
|
|
|
| |
Reviewed-by: thiago
(cherry picked from commit 855ce69f17f570bc91e02bfb34d9e3f1699b3b18)
|
|
|
|
|
|
|
|
|
|
| |
Calling setParentItem is causing the previous opacity/visible updates
to be discarded because the dirty flags were not propagated to the new parent.
Also removed some unnecessary 'markDirty' and 'update' calls.
Task-number: QTBUG-6738
Reviewed-by: bnilsen
|
|
|
|
|
|
| |
We are only interested in getting the posted MetaCall events delivered,
so we can get away with sendPostedEvents() instead of processEvents().
Makes the test also pass on Mac g++ carbon 32.
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
|
|
|
|
|
| |
Avoid traversing the whole child hierarchy when opacity changes unless
there are children with graphics effects.
Reviewed-by: Bjørn Erik Nilsen
|
|
|
|
|
|
|
| |
We need to invalidate the graphics source pixmap cache for both child
items and parent items when changing the opacity of a graphics item.
Reviewed-by: Bjørn Erik Nilsen
|
|
|
|
|
|
| |
Simply skip the updates that are outside the replay widget's bounds.
Reviewed-by: Gunnar Sletta
|
|
|
|
|
|
| |
Don't repeatedly update the pen / brush if no pen / brush is set.
Reviewed-by: Gunnar Sletta
|
|
|
|
|
|
|
|
|
| |
That rare case when we are deleting the last span was not being taken care
of. Unbelievable but true. Auto-test included.
Reviewed-by: Thierry
Reviewed-by: leo
Task-number: QTBUG-6004
|
|
|
|
|
|
|
|
|
|
|
| |
These were processed immediately, so there was a fair chance that we
could end up doing a virtual function call on items that were not fully
constructed. This patch is also an optimization, since we never remove
anything from the vector.
Auto-test included.
Reviewed-by: Jan-Arve
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem occured when doing something in the polishEvent() which
eventually ended up as an update(). The problem was that in
QGraphicsScene::addItem we scheduled a polish event after scheduling
an update, resulting in update requests being processed before polish
requests.
Auto-test included.
Task-number: QTBUG-6956
Reviewed-by: alexis
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Provide configure flag to enable/disable the use of DEF files on Symbian.
A useful side-effect was that it cleaned up how we control DEF files from
qbase.pri and in WebKit.
-nokia-developer still disables DEF files, as it triggers the autotest
exports, which are not frozen into the DEF files.
Disabling DEF files means that there is no BC with previously released
versions of Qt, so this should only be used for development purposes.
.pro files can specify custom locations for DEF files by setting
defFilePath.
Task-number: QTBUG-6556
Reviewed-by: Jason Barron
|
|
|
|
| |
Reviewed-by: Trond
|
|
|
|
|
|
| |
We can't call QCOMPARE from within a nested function, because the
return statement will just exit that function.
VERIFY_COLOR can't be turned into a function this way.
|
|
|
|
| |
Reviewed-by: Sami Merila
|
|
|
|
|
|
|
|
| |
Also use HighlightAllOccurrences to have highlighting during type and
search. Some more refactoring.
Task-number: QTBUG-3335
Reviewed-by: ck
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is a lot of code depending on that pixmaps are flipped
upside down in the gl graphicssystem, so toggling this requires
extensive testing. Since we're anyway questioning the relevance
of this feature (compared to raster + GL viewport) its simply not
worth the effort to fix it properly right now.
Revert "Fixed y-inverted pixmaps on N900."
This reverts commit 57473d5d2a7bd6ae3117f61ff29264a1b790bb01.
|
|
|
|
|
|
|
|
| |
Need to bind the PMV matrix's attributes to their indexes in the
simple shader, which is created in a seperate code path to all the
other shaders. This should fix the qgl autotest failures.
Reviewed-By: TrustMe
|
| |
|
|
|
|
|
|
|
| |
If Avkon components support transparency then dialog background is transparent
enabling rounded corners.
Reviewed-by: Sami Merila
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QmlGraphicsItem doesn't need any parent change notifactions so we can
call the helper class (QGraphicsItemPrivate::setParentItemHelper)
direclty from QmlGraphicsItem::setParentItem. This avoids a lot of unnecessary
instructions related to QVariant constructions as well as virtual
function calls.
I've made the variant pointers explicit in the declaration of
setParentItemHelper so that we don't accidentally call setParentItemHelper
from places where we need parent change notifications.
Task-number: QTBUG-6877
Reviewed-by: alexis
|
|
|
|
|
|
|
|
|
| |
We need this change in order to bypass some of the QVariant itemChange
notifications from QGraphicsItem::setParentItem. All this is internal
stuff and we know what we do, so I don't consider the change too ugly.
Task-number: QTBUG-6877
Reviewed-by: alexis
|
|
|
|
|
|
|
|
|
| |
We don't have to do a full blown QGraphicsItem::setFlag call from
QGraphicsItem::setFlags, only to change the ItemStacksBehindParent
bits. We can do it directly (with care).
Task-number: QTBUG-6877
Reviewed-by: alexis
|
|
|
|
|
|
|
|
| |
Make sure we do cheap tests before the more expensive ones.
This function is called from QGraphicsScene::addItem.
Task-number: QTBUG-6877
Reviewed-by: alexis
|
|
|
|
|
|
|
|
|
| |
The biggest optimization here is "updateAncestorFlags()". It's much
faster to update all the flags rather than trying to enable/disable
certain flags according to the current state.
Task-number: QTBUG-6877
Reviewed-by: alexis
|
|
|
|
|
|
| |
This makes GLSL dumps _significantly_ easier to read.
Reviewed-By: TrustMe
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This has several advantages: First, updating an attribute value
seems to be cheaper than updating a uniform. Second, vertex atribute
values are independent of shader program, which means they persist
across changing of the shader program. This makes code simpler and
reduces GL state changes. Note: Credit goes to Samuel for finding
this little gem. :-)
For the 25920 solid QGraphicsRectItem test case, this gives 10%
improvement on desktop and 27% on the SGX.
Reviewed-By: Kim
|
|
|
|
| |
Reviewed-By: Samuel
|
|
|
|
| |
Task-number: QTBUG-7418
|