| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| | |
git@scm.dev.nokia.troll.no:qt/kinetic into test
Conflicts:
demos/declarative/samegame/content/samegame.js
tests/auto/declarative/qmlecmascript/tst_qmlecmascript.cpp
|
| |\
| | |
| | |
| | | |
kinetic-declarativeui
|
| | |
| | |
| | |
| | | |
Necessary since the SignalEvent class was moved to qstatemachine.h.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There were cases (now covered by autotests) where the state of the
animations could be wrong.
Reviewed-by: janarve
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This breaks the animations in main window because dragging a dock widget
when it is undocked creates another event loop and the Qt events are not
processed any more.
Reviewed-by: Trust Me
|
| | |
| | |
| | |
| | |
| | | |
Merge-Request: 1709
Reviewed-By: Thiago Macieira <thiago.macieira@nokia.com>
|
| | |
| | |
| | |
| | |
| | | |
Merge-Request: 1709
Reviewed-By: Thiago Macieira <thiago.macieira@nokia.com>
|
| | | |
|
| | |
| | |
| | |
| | | |
Reviewed-by: Trust Me
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Reviewed-by: trustme
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There is no reason for it, since they will never overlap.
Left a little space between numbers in case of patch releases.
RevBy: Iain
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This allows the animations to work with the newly integrated dynamic
metaobject
Reviewed-by: Michael Brasser
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QStateMachine framework installs QObject event filters to catch events
in order to triggers the proper transition. But installing a QObject event
filter on a QGraphicsObject gives nothing because QGraphicsView events
filters works differently. In order to make this works we now post
events using QApplication::postEvent in addition to the QGraphicsView
events.
Reviewed-by:andreas
|
| | |
| | |
| | |
| | |
| | |
| | | |
Don't add export declaration for the definition of the variable.
Reviewed-by: Gunnar
|
|/ / |
|
|\ \
| |/
| |
| |
| |
| |
| | |
kinetic-declarativeui
Conflicts:
configure
|
| |
| |
| |
| |
| | |
Mark QGraphicsAnchor::unsetSpacing as reset function of the spacing
property.
|
| |
| |
| |
| |
| |
| | |
The new functions use a lookup table.
Reviewed-by: Trond
|
| |
| |
| |
| |
| |
| | |
"Signal" and "Wrapped" is too generic; prefix with StateMachine.
Reviewed-by: Eskil Abrahamsen Blomfeldt
|
| |
| |
| |
| |
| |
| |
| |
| | |
Also refactored the timer verifications on (un)registerAnimation: we should
never register an animation that has a registeredTimer, but we can unregister
an animation several times.
Reviewed-by: thierry
|
| |
| |
| |
| |
| |
| |
| | |
According to
http://msdn.microsoft.com/en-us/library/ms725496(VS.85).aspx, the
system time resolution is 10-16ms, so we should use multimedia timers
for anything less than 16ms (the worst case).
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Stretch, Repeat and Round are too generic. Renamed to StretchTile,
RepeatTile and RoundTile.
Reviewed-by: Gunnar
|
|\ \
| |/
| |
| |
| | |
Conflicts:
configure.exe
|
| |
| |
| |
| | |
Rev-by: Thiago
|
| |
| |
| |
| | |
Rev-by: Axis
|
| |
| |
| |
| |
| |
| | |
Note that i also removed the #error since the enum is already updated in master
Reviewed-by: Gabi
|
| |
| |
| |
| |
| |
| |
| |
| | |
factor out a dedicated private::read() function based on
private::scan(). this avoids making the latter even more complex in the
process of optimizing it.
Reviewed-By: mariusSO
|
| |
| |
| |
| |
| |
| | |
lastChar needs to be set only when in line mode
Reviewed-By: mariusSO
|
| |
| |
| |
| |
| |
| |
| | |
compilers might or might not have been clever enough to optimize it.
better safe than sorry.
Reviewed-By: mariusSO
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We need a way to control various rendering operations. For example,
whether quality is more important than performance, or the other way
around.
This change also replaces occurences of QPixmapFilter/QGraphicsEffect::BlurHint
(introduced in 1a431e850893b6b162c833f4f148f090e2427dda) with Qt::RenderHint.
Reviewed-by: Samuel
|
| |\
| | |
| | |
| | |
| | |
| | | |
Conflicts:
src/gui/kernel/qwidget_p.h
src/gui/kernel/qwidget_s60.cpp
|
| | |
| | |
| | |
| | | |
RevBy: Trust me
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit b6377f43410b14125a66ffd02acde69cfb6e455e.
The asynchronous handling caused too many headaches with input
methods, which expect the focus status to be updated immediately.
This may break the test case that was originally fixed by this patch
(I cannot find out which one at the moment), but that will have to be
solved in a different way.
Conflicts:
src/corelib/kernel/qcoreevent.cpp
src/corelib/kernel/qcoreevent.h
src/gui/kernel/qwidget.cpp
src/gui/kernel/qwidget_p.h
src/gui/kernel/qwidget_s60.cpp
|
| | |
| | |
| | |
| | | |
Missed qdatastream_p.h in last commit.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
A frequent bug when using QDataStream across platforms where the size
of qreal is different (such as any desktop platform and an ARM device)
is that you end up using different overloads for streaming the value
in and out (e.g. operator>>(double) on desktop and operator<<(float) on
ARM.)
This can leads to crashes and data corruption. To avoid the problem,
we define a single floating point precision for the entire data stream
and allow this to be set by the user. The default is to use 64-bit
precision for all floating point numbers.
Reviewed-by: Samuel
Reviewed-by: Thiago
|
| | |
| | |
| | |
| | | |
Reviewed-by: thiago
|
| | |
| | |
| | |
| | | |
Reviewed-by: Thiago Macieira
|
| |\ \ |
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise the events might creep into the event loop if the state
machine is restarted.
Reviewed-by: Eskil Abrahamsen Blomfeldt
|
| |\ \
| | |/ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The priority specifies whether the event should be posted to what the
SCXML spec refers to as the "external" (NormalPriority) queue, or the
"internal" (HighPriority) queue.
Delayed events are now posted through a separate function,
postDelayedEvent(). That function returns an id that can be passed to
cancelDelayedEvent() to cancel it.
Reviewed-by: Eskil Abrahamsen Blomfeldt
|
| |\ \
| | |/ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Avoid delayed scheduling in the cases where there's no need to
delay it (e.g. when the state machine intercepts a signal or event).
Task-number: QTBUG-4491
Reviewed-by: Eskil Abrahamsen Blomfeldt
|