| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Accessor method for inputMethodQuery was causing crashes.
|
|\
| |
| |
| | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| |\
| | |
| | |
| | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | |\
| | | |
| | | |
| | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | |\
| | | | |
| | | | |
| | | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Resize your window and hit new game
This may invalidate high scores.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
src/declarative/fx/qfxlayouts.cpp
|
| | | |/
| | |/| |
|
| | |\ \
| | | |/
| | | |
| | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | |\ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Remobe another instance of for ... in use.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Don't use the "for ... in" syntax. This is Objective-C 2, which is
only supported on 10.5 and up.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This change ensures that mouse presses received by the scene when there
are no current mouse grabbers trigger hover event delivery. This is
useful when the scene only receives presses, and no mouse moves (e.g.,
disabling mouse tracking on the viewport, or on systems where the
mouse press is the first received event).
Reviewed-by: Michael Brasser
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Change f68fed3 introduced a few regressions in the QGraphicsWidget
autotests. It turned out those autotests relied on behavior that this
fix "fixed". The exact bugs were 1) that setting focus on a window
or a child of a window that isn't active will automatically give that
item focus, despite that its window is inactive (in contrast it should
just set up subfocus and give the item focus when the window is
activated), and 2) that adding a window to a scene that is active did
not immediately activate that window.
So one fix in the test and one in QGraphicsScene. The autotests were
modified so that the respective tests operate on an active scene (by
assigning the scene to an active view). The change in QGraphicsScene
ensures that the first window that gets added to an active scene that
does not have any active windows already, automatically gets activated.
Reviewed-by: Michael Brasser
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Add using to prefer QObject::children() over the obsolete
QGraphicsItem::children() function.
Reviewed-by: Henrik Hartz
|
| | | | | |
|
| | |_|/
| |/| | |
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
componentComplete is always what is wanted.
|
|\ \ \
| | | |
| | | |
| | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The value bindings for rects where using integers.
Use floats instead (as JS only knows about floats
anyway) and make it work with both QRect and QRectF.
Add valuse bindings for QPoint and QPointF.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixed all examples and demos to work after the
changes to Flipable and Rotation3D.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove it's builtin axis and rotation properties.
At least rotation also clashes with
QGraphicsObject::rotation making it a bad idea.
Now Flipable is a pure two sided item, and the
developer/designer will have to set up the flipping
tranformation himself.
|
| | | |
| | | |
| | | |
| | | | |
Also clean up a now unused method.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
removed all the QFxTransform code and converted
QFxItem::transform to use a QmlList instead of a
QList.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Like this we do not clash with the transformOrigin property
in QFxItem.
|
| | | |
| | | |
| | | |
| | | | |
We can simply use boundingRect() instead.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The fx items often call setParent() instead of setParentItem()
so we can't simply remove that method.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is directly supported in QGraphicsItem and we should
use the methods from there.
The transformation handling code in QGraphicsItem needs further cleanups
to get to the agreed model (using a QGraphicsTransform and only
implementing rotate/scale as trivial transformations)
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Consistently use parentItem() as it is consistent with
the naming in QGraphicsItem.
|
| |/ / |
|
| |\ \
| | | |
| | | |
| | | | |
git@scm.dev.nokia.troll.no:qt/kinetic into kinetic-declarativeui
|
| | | | |
|
| |\ \ \
| | | |/
| | |/| |
|
| | | | |
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Conflicts:
configure.exe
src/gui/graphicsview/qgraphicsitem.cpp
src/gui/graphicsview/qgraphicsitem.h
src/gui/graphicsview/qgraphicsitem_p.h
src/gui/graphicsview/qgraphicsscene.cpp
src/gui/widgets/qlineedit.cpp
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The idea of having separate rotationX/Y/Z, shearX/Y, etc.
methods in QGraphicsItem turned out to be not giving us
the flexibility we need and wanted.
The new code now implements a different scheme, where we
keep simple rotate (around z-axis), scale and
transformOriginPoint methods, but remove the other ones.
Instead we now have an additional list of QGraphicsTransform
object. QGraphicsTransform is an abstract class that inherits
QObject. Several specializations are provided and can be
used to transform (and through property bindings animate)
the item.
Reviewed-By: Andreas
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If comparing two variants fails, the failure message will now output
the type and value of the variants (rather than
"Compared values are not the same").
Reviewed-by: Thiago
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Clarified that the format used in QImage::fromData() is the image format,
not the pixel format.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
These structures are only used in versions after 0.922.
Reviewed-by: Donald <qt-info@nokia.com>
|