| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(cherry picked from commit a02eba0de0fcf9a17d489ee1f92977c95d3afd76)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem was reproduced on N97. If the FEP detects that the widget is
full while still editing text, it will try to send those events as
key events instead. Since this screws up the content in the widget,
we stop those events from reaching the widget in the input context.
AutoTest: Passed
Task: QTBUG-12949
RevBy: Miikka Heikkinen
(cherry picked from commit 5ca6264933af60b3cd376b7f08bea008fa69b515)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixed a case where using password mode would lead to Qt
believing that the cursor was one step to the left of where it really
was. This would have the effect of replacing the last character
instead of appending to it, and even crashing if the cursor was all
the way to the left.
The code is also much cleaner this way, but it meant that QTBUG-9867
had to be solved differently this time. We do this by assuming that
and empty FEP update means "erase last character", which seems to
work well in practice.
Also added a long overdue autotest for the FEP input methods. Most
tests pass, but some don't, which I will try to fix later.
Task: QTBUG-9867
Task: QTBUG-12949
RevBy: Miikka Heikkinen
AutoTest: Included
(cherry picked from commit 52cf47565e402dc682038ccaf8d725401802b603)
|
|
|
|
|
| |
QTBUG-13345
(cherry picked from commit b6d47ea4872e188d8da6886cb1922f1a89245825)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After the following sequence:
* Create a TLW, parent1
* Create a child of parent1, and make it a native widget
* Create another TLW, parent2
* Show parent1 and parent2
* Reparent child so its parent is now parent2
* Hide parent1
parent1's backing store should be deleted, when running on Symbian.
Task-number: QTBUG-12817
Reviewed-by: Jason Barron
(cherry picked from commit b5360eb223d5377beb62008fcc1da48f432dc8dd)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After the following sequence:
* widget starts hidden
* Partially reveal widget
* Fully reveal widget
* Hide widget
widget's backing store should be deleted, when running on Symbian.
Task-number: QTBUG-12800
Reviewed-by: Jason Barron
(cherry picked from commit cc1b6475a99994908cbd6309a08fd08614f18221)
|
|
|
|
|
|
|
|
|
| |
There are explicit tests in qdatastream for this. IMO it's wrong,
wrong, wrong, but it's currently abused in the SVG module so we can't
change it.
Reviewed-by: Gunnar
(cherry picked from commit bdcfcc607c1a6744cf1b35eca0914fa96e70071c)
|
|
|
|
| |
(cherry picked from commit 3db2df0a33952223ef0e1a087329ada7f2b2d3ea)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The original code path of QStaticText does not include decoration
drawing, this patch generalized the drawTextItemDecoration()
function to draw decoration for drawText(), then use that to draw
decoration for QStaticText. A helper function called
drawDecorationForGlyphs() is made to allow easier extension for
direct glyphs drawing support.
Task-number: QTBUG-12121
Reviewed-by: Eskil
(cherry picked from commit a1641e27d2e2f5e29362e3737be6b9d75714d138)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Calling QIconModeViewBase::initDynamicLayout() on the second and
successive segments would return QPoint(-1,-1), resulting in a
totally empty area rectangle for all the items while in
QIconModeViewBase::doDynamicLayout(). This rectangle is used to
initialize the BSP tree, and produces an arithmetic exception when
empty.
Furthermore, a rendering bug was also apparent when displaying the
first item of a segment while the last item of the previous segment
was hidden.
Auto-tests included.
Reviewed-by: Olivier
Task-number: QTBUG-12308
(cherry picked from commit 3c7e7992461b1fef37ada68244f1b5b891015bda)
Conflicts:
src/gui/itemviews/qlistview.cpp
tests/auto/qlistview/tst_qlistview.cpp
|
|
|
|
|
| |
Task-number: QTBUG-12991
(cherry picked from commit ba277e9ce92dc40e648f6c83a7cd9f01dd33b886)
|
|
|
|
|
| |
Task-number: QTBUG-12994
(cherry picked from commit d30921f13dc74a3e05a3f29c0c45147823f2a064)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit ebbab30af417dfbf3df47dec15c0e2f8d6a30fa6,
which broke fill / outline consistency, and when trying to fix that
by rounding the fill the same way that broke rendering in Creator.
Unfortunately the X11 paint engine is too sensitive to changes, there
have already been tons of patches to make it as consistent as possible.
It's simply not possible to get the same rounding for both fill and
outlines and at the same time have consistency between fill and outline
(no holes or fill outside the outline), while using the integer based
Xlib rendering API. Hopefully in 4.8 we'll switch to raster and the X11
paint engine will be a legacy.
Reviewed-by: Trond
(cherry picked from commit 041a68007413a20a9a9c97d0f2f04f9e03428f67)
|
|
|
|
|
|
|
|
| |
These are owned by the root and must not be destroyed by child lists.
Task-number: QTBUG-12771
Reviewed-by: Bea Lam
(cherry picked from commit 4026b2c7bc91f8f25f73b182687d5d2bed823217)
|
|
|
|
|
| |
QTBUG-12729
(cherry picked from commit ee7c3b576ced47d3b68da1913cdf6995144bddd2)
|
|
|
|
|
|
|
|
|
|
| |
The problem was in the toggleDrawer function. We were not checking the
status of the last transition before setting the new transition, so
all the transition were treated as non-intentional.
Task-number: QTBUG-11373
Reviewed-by: Prasanth
(cherry picked from commit 725d8e061ededee9a5ddf0914aabd0f6aa2ee741)
|
|
|
|
|
|
|
|
| |
Also emit the signal at the very end, so people can rely on the resize
event to adjust some stuff in their item.
Reviewed-by:yoann
(cherry picked from commit 3ee89bc0830f69d44f272eff5a0c886bff33c92e)
|
|
|
|
| |
(cherry picked from commit 62968f33452016b31020e524fa6ba6d2cefd0278)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a line break was detected, we would retain the value of the
right bearing for the character after the break instead of resetting it
to the right bearing of the previous value. This could in some cases
cause the bounding rect of the text to be wrong, and could cause
unnecessary horizontal scrollbars to pop up. It was especially visible
when using WrapAnywhere. Visible e.g. in the compile output in Creator.
Done-by: mae
Reviewed-by: Eskil
Reviewed-by: Lars
(cherry picked from commit c5fa9eb1cb02d979502e2c9918d752c6708fb406)
|
|
|
|
|
|
|
|
|
|
| |
This fixes Westpoint Security issue with Advisory ID#: wp-10-0001.
Before, we would allow wildcards in IP addresses like *.2.3.4 ; now,
IP addresses must match excatly.
Patch-by: Richard J. Moore <rich@kde.org>
Task-number: QT-3704
(cherry picked from commit 846f1b44eea4bb34d080d055badb40a4a13d369e)
|
|
|
|
|
|
|
|
|
| |
When a Repeater was used as the child of an Item binding to childrenRect,
the item change listener was being added twice for the items created
by the Repeater.
Task-number: QTBUG-12722
(cherry picked from commit 6feb5b75ce96aeeefee189af003949db8c031519)
|
|
|
|
|
|
|
|
|
| |
It's the scene itself that acts as a focus scope, not the top-level
item.
Task-number: QTBUG-12682
Reviewed-by: Aaron Kennedy
(cherry picked from commit 94b1c07c31ab84d30b198cb23291a48f98164827)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SpringFollow was turned into SpringAnimation so it could be
used inside a Behavior. This patch completes the work and makes
it usable inside a transition.
This is the documented behavior of SpringAnimation, the patch
is essential to make SpringAnimation work consistently.
Reviewed-by: Michael Brasser
Task-number: QTBUG-12141
(cherry picked from commit 33203efb786de9aebc6e05d1b4878d89e86ac456)
|
|
|
|
|
| |
QTBUG-12590
(cherry picked from commit 1fc6cab93ba2d067fadcd0979640c32aa1d5ae4a)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Task-number: QTBUG-12142
Reviewed-by: Warwick Allison
This patch brings ability to switch QML Viewer's orientation between auto-orientation (=follow sensor),
portrait and landscape orientations (lock orientation) on Symbian. It provides same orientation options as
Qt Creator 2.1's Qt QML Standalone Application creation wizard. Also, menu item rotateOrientation now
works on Symbian, but it's hidden when orientation mode is set to auto-orientation.
Property runtime.orientation has been switched back to supporting four-way orientation on Symbian, previously
it only updated values between portrait and landscape. If your application only supports landscape or portrait
modes, just don't react to the inverted orientations.
Added orientation example screenorientation under examples/declarative.
The patch includes a fix for calculator example, which rotated to wrong direction when switching from portrait
to landscape. Also, improved qdeclarativeviewer unit tests. Changes have been tested to work on Windows,
Linux and Symbian^3.
(cherry picked from commit e62f266a7642e675e9d235a1f54a6b5746500d48)
|
|
|
|
|
|
|
| |
Task-number: QTBUG-10643
Task-number: QTBUG-11376
Reviewed-by: Jason Barron
(cherry picked from commit 3695cb25e4a53921880cfea4d4c731df44fa4396)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On the X11 paint engine, when rendering lines with float coordinates,
the lines were one pixel off if the decimal was > 0.5.
This fixes the WebKit bug https://bugs.webkit.org/show_bug.cgi?id=42248
Autotest by Yoann Lopes.
Reviewed-by: Simon Hausmann
Reviewed-by: Yoann Lopes
Reviewed-by: Andreas Kling
(cherry picked from commit ebbab30af417dfbf3df47dec15c0e2f8d6a30fa6)
|
|
|
|
|
|
|
|
|
|
|
| |
PathView handles its own mouse interaction, but lacked properties
similar to those in Flickable to determine when it is stationary.
This made it impossible to start an animation when the view stops moving,
for example.
Task-number: QTBUG-12497
Reviewed-by: Warwick Allison
(cherry picked from commit eae48b410cc28b83433b7dcba379a31aae2ce2df)
|
|
|
|
|
| |
2f582953ecfc53f217317f58e4fc75b5b51a1126
(cherry picked from commit 34691d27d03abc0c8f940b4a0a3cda4cd308642e)
|
|
|
|
|
| |
Task-number: QTBUG-12397
(cherry picked from commit 3e8597ff6029d33d629191370d9fed7d37d3962a)
|
|
|
|
| |
Reviewed-by: MArtin Jones
|
|
|
|
|
|
|
|
|
| |
This commit also updates QPalette's documentation regarding the current
ColorGroup and operator==.
Task-number: QTBUG-697
Reviewed-by: ogoffart
(cherry picked from commit 24cdab32de2abd8669f281dd54c8da1124514915)
|
|
|
|
|
|
|
|
| |
Broke signal handlers in QML
Task-number: QTBUG-12335
Reviewed-by: Aaron Kennedy
(cherry picked from commit ddb5e1eef379c7f32a594d91b00ff3514c46b62a)
|
|
|
|
|
|
|
|
|
|
| |
The wantsFocus property has been renamed to activeFocus, to better
reflect its value. Reading and writing the focus property is also now
consistent -- this property represents focus within a scope. Other small
changes were made to keep things consistent with the new naming.
Reviewed-by: Aaron Kennedy
(cherry picked from commit 21806ff0921641b4e4d9d39721ab4ebeae74dddc)
|
|
|
|
|
|
|
|
|
| |
Ancestors of the item with focus should only report wantsFocus as true
when they are a FocusScope or a top-level item.
Reviewed-by: Aaron Kennedy
Reviewed-by: Yann Bodson
(cherry picked from commit 686fca1c78e6d4d2ba597dd75d982c76647c7707)
|
|
|
|
|
|
|
|
|
| |
This allows dragging a MouseArea that contains a clickable MouseArea,
for example.
Task-number: QTBUG-12323
Reviewed-by: Michael Brasser
(cherry picked from commit 5dd0dfcd7a079065f99c6149c15b58e69f302729)
|
|
|
|
|
|
|
|
|
|
|
| |
Otherwise a Behavior may mistakenly not be triggered. This situation
can arise when the property in question has been manipulated via the
property system, followed by a direct function call (which correctly
bypasses the Behavior), followed by a another change via the property
system.
Task-number: QTBUG-12295
(cherry picked from commit 64833c0a648211f3fe7547436f022edc0ceb51ac)
|
|
|
|
| |
(cherry picked from commit 5efd577b1aea64f422e08ca8d54e041fa4b20783)
|
|
|
|
|
|
|
|
|
| |
The boundingRect depended upon the image cache which may not become
valid until after boundingRect is called.
Task-number: QTBUG-12291
Reviewed-by: Michael Brasser
(cherry picked from commit 3aeafb4839f49f524f10eae65be27fd189d37060)
|
|
|
|
|
|
|
|
| |
We need to create our cached image in boundingRect() if it doesn't
already exist, to prevents painting errors.
Reviewed-by: Warwick Allison
(cherry picked from commit 6c3cf7e2c5868bc77ffa66059889eda3132531b3)
|
|
|
|
|
|
|
|
| |
having different contents
Task-number: QTBUG-12339
Reviewed-by: Martin Jones
(cherry picked from commit 0767c2ff719a35c16c72fac97e6ff612e8c71e21)
|
|
|
|
|
|
|
|
| |
... and percentage is useless.
Task-number: QTBUG-12282
Reviewed-by: Warwick Allison
(cherry picked from commit 78a01438e5a37fd1778924f73ca8bfa55960b0d0)
|
|
|
|
|
|
|
|
| |
height explicit
Task-number: QTBUG-12273
Reviewed-by: Michael Brasser
(cherry picked from commit 164b2b54922d87a44a60efe6dbbe2fa3b7716820)
|
|
|
|
|
|
|
| |
Also parent them back to the VIM to ensure correct destruction.
Task-number: QTBUG-12261
(cherry picked from commit 17cc89e918a969d85d2b46631ee8743288c7586d)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The way we detect the end of a default argument does not take in account
template parametter.
It is unfortunatelly not trivial to do it properly without semantic information
So we will use heuristics and if the number of < matches the number of >
we consider it is a template. Or if we have a '=' we consider it is not a
template.
Task-number: QTBUG-12260
Reviewed-by: Roberto Raggi
(cherry picked from commit 4da1a3b63445c04d4ca4acae448e9b6b046938c3)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This only happens when the ItemHasNoContents and ItemClipsChildrenToShape
flags are set. Problem is that items with no content are threated as 'dummy'
items, which means they are never drawn or 'processed' otherwise, so the
cached bounding rect is not reliable/usable. This means that in case of
changing the geometry of such items, its children always have to take
care of invalidating the occupied areas and the update can not be
clipped to the item's bounding rect.
Regression after commit: c1c7dbf2
Auto test included.
Task-number: QTBUG-11504
Reviewed-by: yoann
(cherry picked from commit 4df9c96e2c213c39924e22e02621b0c61e83f8fe)
|
|
|
|
|
|
|
|
|
| |
When the sections were moved calling logicalIndex on what was already
a logical index messed up the hidden sections.
Task-number: QTBUG-12268
Reviewed-by: Gabriel
(cherry picked from commit 8517f787b798d9e300438404aab359de2acc0978)
|
|
|
|
|
| |
Task-number: QT-3613
(cherry picked from commit 2c574ed1bf9943130fb9af5435b557a47e3c462b)
|
|
|
|
|
|
|
|
| |
QDeclarativeVisualDataModel::stringValue() did not handle
QList<QObject*> model types.
Task-number: QTBUG-12005
(cherry picked from commit b6251d31652232a6ac3a5dff54ad4229542089b1)
|
|
|
|
|
|
|
|
|
|
|
| |
The scale of the delegate was used to offset the item. This was a
bad way of making the item appear to be positioned correctly when
the default transform origin was the top-left. Now that transform origin
is center, it is obvious that it was a bad idea.
Task-number: QTBUG-12245
Reviewed-by: Michael Brasser
(cherry picked from commit 5572ec653fe735c4f413195c1ef34382aa8c6105)
|