| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
| |
(cherry picked from commit b325c90e5a0e5088aa8723d943f4c38b14048bd7)
|
|
|
|
|
| |
Seems some platforms don't have it.
(cherry picked from commit 7725da34a828df00feb289515c11fa8aea1a55d8)
|
|
|
|
|
|
|
|
|
|
|
| |
Allow essentially unbounded dragging once drag.target is set. The previous
default of contraining the dragging to 0,0 (i.e. no drag) was unintuitive
for learners. It's rare that unbounded is actually what you want, but it
makes it much easier to get started with the element.
Task-number: QTBUG-11184
Reviewed-by: Martin Jones
(cherry picked from commit b2f90dedbeac285338af07fbffaec97ceaf0876f)
|
|
|
|
| |
(cherry picked from commit 07ebc9161263c04dc072b9fc2a922b9665cbe7be)
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
| |
Task-number: QTBUG-12322
Reviewed-by: Aaron Kennedy
(cherry picked from commit 0b83a2161261be525f01359397ab1c8c34827749)
|
|
|
|
|
| |
Task-number: QTBUG-12292
(cherry picked from commit 6d8b3453b6b4b151c777ad541ab25ca6bacc7381)
|
|
|
|
|
|
|
|
| |
... 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)
|
|
|
|
| |
(cherry picked from commit c95889b7896dc5418841ef72326d99296943e616)
|
|
|
|
|
|
|
|
|
| |
transformOriginPoint is undocumented for a reason. It shouldn't be used
by Item. Added some docs to assist find the right way, i.e. Scale and
Rotation elements.
Task-number: QTBUG-12265
(cherry picked from commit 06ef198e0812b514c261ef8f7c82db754450f1fa)
|
|
|
|
|
|
|
|
|
|
| |
Using this property on Item will break transformOrigin property. We
have never documented it. It should not have been used. Now it is
enforced as best we can.
Task-number: QTBUG-12265
Reviewed-by: Aaron Kennedy
(cherry picked from commit 7fb140b63f03b96064ded4ec6f2ec7c93e87b825)
|
|
|
|
|
|
|
| |
Also parent them back to the VIM to ensure correct destruction.
Task-number: QTBUG-12261
(cherry picked from commit 17cc89e918a969d85d2b46631ee8743288c7586d)
|
|
|
|
|
|
|
| |
Geir will replace it soon with a link to a new "Getting Started" page.
Task-number: QTBUG-12176
(cherry picked from commit eaee97cf48feecc18d6154d3939fd4adb93ba74f)
|
|
|
|
|
| |
Task-number: QTBUG-12132
(cherry picked from commit d9f5b8742f84124c3c0e2bdbd7b860dce2bc2225)
|
|
|
|
|
| |
RevBy: Trust me
(cherry picked from commit 4280c4c72fcd04e9061e08fb30f73fbd9f88b850)
|
|
|
|
| |
This reverts commit 8932980a72653aa9695a6d0f1c8ce6077506d33c.
|
|
|
|
| |
This reverts commit ba2d235356b551aab2d07a275069b16b6776c31f.
|
|
|
|
|
|
|
|
|
|
| |
While generating the QDragMoveEvent, we were always reusing the last
drop action set by the user. This is not correct, we should copy the action
only if a valid action set before. This is the behavior on Windows.
Task-number: QTBUG-9486
Reviewed-by: Denis
(cherry picked from commit 88410105978d5fb4344207cd5d296057ced0f27d)
|
|
|
|
|
| |
Task-number: QTBUG-11512
(cherry picked from commit d8908922f339892fee4275a433e2bf6da87ae055)
|
|
|
|
| |
(cherry picked from commit e0a102ee171ddcebb1104d98d8a4ff4993e91c1d)
|
|
|
|
|
|
| |
Task: QTBUG-11927
RevBy: Trust me
(cherry picked from commit 77bd18e7636a65c3a3be5e8e912484e8dc5fee02)
|
|
|
|
|
|
|
|
|
| |
Since we cannot extract to the epocroot (it is considered R/O), we
extract the header and the dso to the temporary build directories and
include them from there.
RevBy: Trust me
(cherry picked from commit c578c6c1d6dc2f3bb6cc53abb8da2e706a249f02)
|
|
|
|
|
|
| |
Task: QTBUG-11927
RevBy: Trust me
(cherry picked from commit f1d92df9ba30c1a7e97b29dd069db8e7bbb25636)
|
|
|
|
|
| |
Reviewed-by: Daniel Molkentin
(cherry picked from commit 2fd446db8842e78af22d63acbb03a96ca242bb35)
|
|
|
|
|
|
|
|
|
| |
The problem was that the QT_BEGIN_NAMESPACE was in the wrong place.
I moved it 10 lines before and the problem is gone.
Task-number: QTBUG-12262
Reviewed-by: Prasanth
(cherry picked from commit b0998a44a5dc384a6cf65c1d5910cb3dd40620cf)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
|
|
| |
QTextBlock::layoutDirection() doesn't exist, and the QStaticText
constructor no longer takes a size argument.
Task-number: QTBUG-12072
Reviewed-by: Fabien Freling
(cherry picked from commit 04bc2b1f37750a2afbb88521001758249a8df383)
|
|
|
|
|
|
|
|
|
| |
Otherwise it is not possible to build projects outside of the Qt tree
without installing Qt to the SDK first.
Task: QTBUG-11727
RevBy: Trust me
(cherry picked from commit 11d626de5fd87fc8cbd9d685bde8217c7ad7fae6)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
| |
Task: QTBUG-11385
RevBy: Jason Barron
(cherry picked from commit d9e75d77ac3da86c32d280895beac2936d8869ca)
|
|
|
|
|
|
|
|
|
|
| |
If Oracle national char types use different charset(NLS_NCHAR_CHARSET) with
the database charset (NLS_CHARSET), the oci client need to set OCI_ATTR_CHARSET_FORM
to SQLCS_NCHAR instead of SQLCS_IMPLICIT.
Task-number: QTBUG-10919
Reviewed-by: Michael Goddard
(cherry picked from commit f8f255553f3640355d3e196e100778256741701c)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The reason for the infinite recursion was that
QAccessibleTitleBar::object() returned the titlebar's dockwidget.
This could lead to a problem when the AT client tried to
traverse the accessibility hierarchy:
As a response to QAXChildrenAttribute (retrieve children) on a dock
widget node, it would register it's children in the
hierarchy manager. In this case, the object registered for the titlebar
interface was the QDockWidget.
In order to do further traversal, the bridge could call
queryAccessibleInterface on the list of retrieved children to get the
QAccessibleInterface for those objects, however, that would return the
QAccessibleDockWidget interface that we just had traversed,....
Task-number: QTBUG-6843
Reviewed-by: Carlos Manuel Duclos Vergara
(cherry picked from commit 64b9e63f4f9162c1af299b1355e84b0e616ad768)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QSymbianBitmapDataAccess is used to provide access to the bitmap heap
in a manner that locks correctly on all platform versions. The
heapWasLocked variable was meant to protect against the case where
the heap is locked recursively. However, it failed to take into
account the case where the same QSymbianBitmapDataAccess object was
used to lock recursively. In this case the variable would be changed
to true on the second lock, which means that the lock would never be
released again.
This was fixed by making the access reference counted instead. Since
the bitmap heap lock is global, the refcount was made global as well.
Task: QTBUG-11129
RevBy: Jason Barron
AutoTest: Works again. It was hanging before this fix.
(cherry picked from commit d4cc1dcea5b4116767cfee0ec45bfba72dc011ff)
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
| |
Task-number: QT-3584
Reviewed-by: Trustme
(cherry picked from commit 30341a6f9e57caac3ec19e02ffd67164d43c0453)
|
|
|
|
|
| |
Task-number: QTBUG-10439
(cherry picked from commit 75db37022a9fd479e2a446b57e774eaf8e3e73ea)
|
|
|
|
|
| |
Reviewed-By: Alessandro Portale
(cherry picked from commit ebf650dd893a8f6ace2252cd2a18ee895520f29d)
|
|
|
|
| |
(cherry picked from commit 368dd3c234b9011ab8a8506b50fce6f55694199c)
|
|
|
|
|
| |
Reviewed-By: Jason McDonald
(cherry picked from commit a545e26e1183133f4a66cb9a3bcd9051e2d77894)
|
|
|
|
|
|
|
| |
It relied on the now missing pixmap property. Since it isn't used, it
doesn't seem worth the effort to update it to use a declarative image
provider instead.
(cherry picked from commit 75131b7a1bfeeb033ea5b8bf62d50cc3d82d757e)
|
|
|
|
|
|
|
|
| |
Some people didn't figure it out intuitively, so extra help is now
provided.
Task-number: QTBUG-11868
(cherry picked from commit 8668f245b69da455ac7fe1d0a599226c1d6b9580)
|