| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
the default animation concept, since this is its intended use.
|
|
|
|
| |
assert in the state machine which needs to be debugged.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Accessing the event can be useful. E.g., onEntry() can do some
common event processing regardless of which transition caused the
state to be entered; onTransition() can be used in combination
with eventTest(), where eventTest() would first check that the
input matches some criteria, and then the actual processing of that
input would be done in onTransition.
|
| |
|
|
|
|
| |
overrides the virtual function.
|
|
|
|
| |
response.
|
|
|
|
| |
loop. Also make sure we set the direction to an angle within 360 degrees.
|
|
|
|
| |
immediately for reverse actions, thus immediately stopping them.
|
| |
|
|
|
|
| |
based on the meta-object system.
|
|
|
|
|
|
| |
and then fire. One of them has an error, which causes it to enter its error
state. The errorstate example has been changed to handle this by disabling
the tank. The rest of the tanks will keep working.
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
examples/animation/sub-attaq/states.cpp
|
| | |
|
| | |
|
| |
| |
| |
| | |
Result of API review.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Result of API review. A == comparison of the modifiers is not useful.
The common case is you want to test if one or more modifiers are set,
i.e. a mask check.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Decided in API review. The intention of QHistoryState not being
constructible was so that people wouldn't subclass it and reimplement
onEntry()/onExit(), thinking that those functions would actually get
called (which they won't). However, we recently added the entered()
signal to QAbstractState, so people are going to connect to it and
ask why they never get the signal for a QHistoryState. We might as
well make QHistoryState constructible and just document that it
doesn't make sense to subclass it.
|
| |
| |
| |
| | |
It's useful and it's simple for us to expose, so let's.
|
| |
| |
| |
| |
| | |
if there is a transition from one of them (even if the target state of the
transition is inside the region.)
|
| |
| |
| |
| |
| |
| | |
Added cannon firing. There are some problems left: For some reason the parallel
state group does not work properly, so only one tank moves even if you add more.
There also seems to be something wrong with historyState->setDefaultState().
|
| | |
|
| |
| |
| |
| | |
work at all.
|
|/
|
|
|
| |
one such plugin will have a run time error, so the game server needs to use
errorState for handling errors.
|
|\
| |
| |
| |
| | |
Conflicts:
examples/animation/piemenu/qgraphicspiemenu_p.h
|
| |
| |
| |
| |
| |
| | |
use case for this, so it has been removed. If the requirement arises we can
add it back in later. Since it no longer makes sense to have it in
QAbstractState, the RestorePolicy enum has been moved to QStateMachine.
|
| | |
|
| |
| |
| |
| |
| | |
have changed to something which is more intuitive, so it is no longer useful
for this case.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It just didn't give us that much.
Typically you just reimplement onEntry/onExit/onTransition
when you want to do something.
We go back to the signals-and-slots approach: states have
entered() and exited() signals that you can connect to.
It's still possible to have an action-based API, but then
you build it on top of the core API, which is OK.
Replacing 4 public classes (and one layer in the hierarchy)
with 2 signals feels good.
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
| |
sub-attaq doesn't use anymore animation private headers
|
| |
|
|\ |
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
src/gui/graphicsview/qgraphicsitem.cpp
|
| | |
| | |
| | |
| | | |
setMargin() is deprecated.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
have a version number, so we do not have to update it each release.
Task-number: 251352
Reviewed-by: TrustMe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
marked getInt() as since Qt 4.5 and finally modified the StandardDialogs
example to reflect the fact that getInteger() is deprecated.
Task-number: 251288
Reviewed-by: nrc <qt-info@nokia.com>
BT: Yes
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It seems that Cocoa is much more strict about coalesced updates than
Carbon ever was. The upshot of this is that some examples that "worked"
after a fashion in Carbon, do not exhibit good frame rates with Cocoa.
The reason why is that apparently Cocoa will decide to flush to the
screen every time a timer fires. If you have a lot of timers that are
all dependent on doing on update to the screen, you will get undesirable
effects.
Thankfully, it is possible to adjust the examples to follow best
practices and get a good result. So, we now only do the animation once
using QGraphicsScene::advance(). We are also able to make the mice less
heavy (no QObject subclass). I've updated the docs and someone on the
doc team has kindly volunteered to go through them.
Reviewed-by: Andreas
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Otherwise, for people who install Qt (everyone outside Nokia), the
animation file isn't present.
Reviewed-by: Trust Me
BT: yes
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
commit e67776ff836b1e761dd1db1945daddc6394b6a54
Author: David Boddie <dboddie@trolltech.com>
Date: Thu Mar 26 17:47:42 2009 +0100
Doc: Added missing file.
Reviewed-by: TrustMe
|