| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\ |
|
| | | |
|
| |\ \
| |/
|/| |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
When the variant is invalid the shared is not destroyed.
We even can avoid the creation of the PrivateShared if we know the
variant is invalid
Reviewed-by: Thierry
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Constructing a variant of a pointer type was previously quite slow:
QVariant had no information it was a pointer. It had to create a
QVariant::PrivateShared, ask the QMetaType for a constructor (slow as it
involve locking mutextes) and allocate a pointer.
By detecting a pointer in qVariantFromValue, we can store the pointer
value dirrectly in the Variant union. We then avoid 2 allocations,
and the expensive locking in QMetaType::construct
Reviewed-by: Thierry
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
This is private API
Reviewed-By: Trustme
|
| | |
| |
| |
| |
| |
| | |
This is private API
Reviewed-By: Trustme
|
| | |
| |
| |
| |
| |
| | |
It seems the winId can change during a WindowStateChange event too.
Reviewed-By: Trustme
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
The PBO code path causes a crash on certain AMD graphics cards, plus
seems to perform worse than the straight forward glTexImage2D code path
on several configurations.
Task-number: 257353
Reviewed-by: Gunnar Sletta
|
| | |
| |
| |
| |
| |
| | |
eventObject was a horrible name. The documentation already used the
term "event source", so let's call it that.
Agreed with Eskil.
|
| | |\ |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
JSC::Debugger::exceptionThrow event was moved _before_ stacks
unwinding so there is possibility to check stack state before it's
deletion.
Missing functionExit event was added in Interpreter::unwind()
Reviewed-by: Kent Hansen
|
| | | |
| | |
| | |
| | | |
Reviewed-by:TrustMe
|
| | | |
| | |
| | |
| | | |
Reviewed-by: Samuel
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
operators and 64 bit values in QVariant. This is probably a compiler bug. Workaround is flagged with Q_CC_RVCT specific just in case, but should work for all compilers."
This reverts commit 85a1f7888bd48d5857de2b7c6304a334350fd054.
Conflicts:
src/corelib/kernel/qvariant.cpp
tests/auto/qvariant/qvariant.pro
I cannot reproduce this anymore with the latest RVCT, not even in
S60 3.1.
RevBy: Miikka Heikkinen
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This was done because I initially thought that KRequestPending was a
bit flag, but it turns out it's just an int value, so == is more
correct.
RevBy: Iain
AutoTest: Passed
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Private directory is not always in C-drive.
RevBy: Trust me
|
| | | | |
| | | |
| | | |
| | | | |
RevBy: Trust me
|
| |\ \ \ \ |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
I had a "typo", probelmatic line have be just swaped.
Reviewed-by: jbarron
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It is not currently supported anymore after QtScript switched to the
JavaScriptCore backend.
RevBy: Trust me
|
| |\ \ \ \ \
| |/ / / / |
|
| | | | | | |
|
| |\ \ \ \ \
| |/ / / /
|/| | | /
| | |_|/
| |/| | |
Conflicts:
examples/graphicsview/graphicsview.pro
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
QAbstractScrollArea
We send the Touch* events filtered from the viewport to the scroll
area's default handler so that we can take advantage of the default
handling in QWidget. But we also need to ignore Touch* events in
QAbstractScrollArea::event() so that we don't get the events twice
(once from the filter, and again if propagated).
Reviewed-by: Richard Moe Gustavsen
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The default cursor on QWS is loaded as an 8bit QImage.
Blitting that one is really slow so we better convert
the image into a fast format before using it.
Based on a patch by Lars.
Reviewed-by: Tom
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously, length of linuxfb device's path must be 8 and start with "/dev/fb".
Reviewed-by: Paul
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Request focus before requesting a geometry. This makes it much more
likely that the initial paint will be done after the window is active.
Task-number: 255828
Reviewed-by: Tom
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
AVR32 doesn't support non-aligned access. (Contributed patch)
Task-number: 255495
Reviewed-by: Paul
|
| | | | | |
|
| | |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
git@gitorious.org:+openbossa-developers/qt/openbossa-clone
Conflicts:
src/gui/graphicsview/graphicsview.pri
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Those are:
* setAnchorSpacing()
* anchorSpacing()
* unsetAnchorSpacing()
Autotests for the two last ones are missing though..
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The changes are:
* Move enums in QGraphicsAnchorLayout::Edge to Qt::AnchorPoint.
Prefix them with Anchor since they are not edges in general.
* Rename anchor() to addAnchor()
* Rename anchorCorner() -> addCornerAnchors()
* Rename anchorWidth() -> addLeftAndRightAnchors()
* Rename anchorHeight() -> addTopAndBottomAnchors()
* Rename anchorGeometry() -> addAllAnchors()
* remove the overloads that take a spacing argument, and add
setAnchorSpacing() to accommodate for that.
* Added anchorSpacing() (implementation missing)
* Added unsetAnchorSpacing(). (implementation missing)
* made sizeHint() protected.
Updated all examples and autotest to reflect this API change.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Also, only include the "name" member to AnchorData if we are compiling
in debug mode.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Functionality-wise it should be the same, its just a bit less code.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Don't assume that m_item is always a QGraphicsWidget
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit implements what's described in the previous commit
QGraphicsAnchorLayout: fix expected values for parallel test
When filling the sizeAt* values (the three points used for interpolation
when setting geometry), now sequential anchors distribute the sizes
to the children in a fair way, i.e. proportionally in relation to the
existing min/pref/max hints.
Each value is defined in relation of the pref (either as a shrinkage in
pref or a grow in pref). In both cases the shrinking/growing factor is
the same for all children.
When we implement support for QSizePolicies, this distribution might be
changed by setting size policies for a certain item or anchor.
This makes two tests work -- so no more expected fail. Also fixed a typo
in one test's expected results.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When creating an anchor we might have to create the edges for an item
if the item is new. In this case both dimensions are affected. The
call is clearly missing since createItemEdges() declared this
dependency via Q_ASSERT.
Patch from Jan-Arve.
Reviewed-by: Caio Marcelo de Oliveira Filho <caio.oliveira@openbossa.org>
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
For debugging purposes, if QT_ANCHORLAYOUT_NO_SIMPLIFICATION
environment variable is set, the layout won't use
simplification. Useful for some debuggings.
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When traversing the graph looking for calculating the distances, also
enter inside the complex edges to find (and calculate) the distances for
the vertices that were simplified.
This require a little tweak in the traversal, now we can't always skip an edge
when both vertices are already visited, because complex anchors can hide
vertices inside (a sequential anchor in practice remove vertices from the
full graph).
As a bonus we now pass on the 'example' test (as expected) and the
example now works fine.
Signed-off-by: Caio Marcelo de Oliveira Filho <caio.oliveira@openbossa.org>
|
