summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* add missing QT_END_HEADERKent Hansen2009-04-291-0/+2
|
* replace QState::Type with QState::childMode propertyKent Hansen2009-04-298-29/+70
| | | | Result of API review.
* Add test that property assignments set on parallel states are actuallyEskil Abrahamsen Blomfeldt2009-04-291-3/+40
| | | | applied after entering.
* Adapt to recent API changes and bug fixes.Eskil Abrahamsen Blomfeldt2009-04-291-2/+6
|
* Remove QEXPECT_FAIL because e06c2e15 fixes this test as well.Eskil Abrahamsen Blomfeldt2009-04-291-1/+0
|
* Compile against new QHistoryState API.Eskil Abrahamsen Blomfeldt2009-04-291-2/+2
|
* Merge the two queries for entry states to support having history states asEskil Abrahamsen Blomfeldt2009-04-292-71/+113
| | | | the initial state. Done by No'am, integrated by me.
* rename a few properties and methodsKent Hansen2009-04-297-21/+21
| | | | Result of API review.
* modifiers --> modifiersMaskKent Hansen2009-04-299-33/+98
| | | | | | 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.
* compileKent Hansen2009-04-291-0/+1
|
* kill unnecessary qmake variable modsKent Hansen2009-04-291-3/+0
|
* make history state constructibleKent Hansen2009-04-299-59/+78
| | | | | | | | | | | 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.
* say hello (again) to QAbstract{State,Transition}::machine()Kent Hansen2009-04-296-39/+47
| | | | It's useful and it's simple for us to expose, so let's.
* add animationsEnabled propertyKent Hansen2009-04-293-8/+47
|
* move assignProperty() to QStateKent Hansen2009-04-299-56/+58
| | | | Doesn't belong in the abstract base class.
* kill StateFinished from docsKent Hansen2009-04-291-1/+0
|
* Work around an oddity in parallel states that causes all regions to exitEskil Abrahamsen Blomfeldt2009-04-281-4/+4
| | | | | if there is a transition from one of them (even if the target state of the transition is inside the region.)
* Add a test for the semantics of transitions from a region in parallel states.Eskil Abrahamsen Blomfeldt2009-04-281-0/+47
| | | | | | | This test checks for the behavior I expected, but that's apparently not how it's defined in the SCXML algorithm. Currently it XFAILs, and we'll either have to fix the algorithm or the test when we get word back on what the correct semantics are.
* Some updates to the errorstate example.Eskil Abrahamsen Blomfeldt2009-04-2812-126/+270
| | | | | | 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().
* kill StateFinished event type since it doesn't exist anymoreKent Hansen2009-04-281-2/+1
|
* compile after api changesKent Hansen2009-04-283-8/+8
|
* replace QStateFinished{Event,Transition} by QState::finished() signalKent Hansen2009-04-2710-423/+23
| | | | | Not worth it having two public classes when the same can be achieved by having a signal.
* make the entry/exit order well-defined for all combinations of statesKent Hansen2009-04-271-4/+18
| | | | | | Comparing pointers meant that the order could be different each run. Now the entry/exit order will be consistent, even for states that are in disjoint parts of the hierarchy.
* Really broken plugin for errorState. Don't try to use this yet, it doesn'tEskil Abrahamsen Blomfeldt2009-04-243-0/+115
| | | | work at all.
* Unfinished tank AI game. The idea is that you plug in AIs for the tanks, andEskil Abrahamsen Blomfeldt2009-04-248-0/+619
| | | | | one such plugin will have a run time error, so the game server needs to use errorState for handling errors.
* Merge branch 'kinetic-statemachine' into kinetic-animationsKent Hansen2009-04-2442-2484/+1178
|\ | | | | | | | | Conflicts: examples/animation/piemenu/qgraphicspiemenu_p.h
| * Merge branch 'kinetic-animations' into kinetic-statemachineKent Hansen2009-04-241-4/+4
| |\
| * | Remove API for setting specific restore policies on states. We have no clearEskil Abrahamsen Blomfeldt2009-04-239-133/+73
| | | | | | | | | | | | | | | | | | 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.
| * | Compile.Eskil Abrahamsen Blomfeldt2009-04-231-2/+0
| | |
| * | Remove specific RestorePolicy per state from example. The semantics for thisEskil Abrahamsen Blomfeldt2009-04-233-15/+0
| | | | | | | | | | | | | | | have changed to something which is more intuitive, so it is no longer useful for this case.
| * | kill the stateactions apiKent Hansen2009-04-2236-1720/+148
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | Test for overriding default animations. This test defines the order ofEskil Abrahamsen Blomfeldt2009-04-221-0/+247
| | | | | | | | | | | | | | | | | | | | | | | | | | | precedence: 1. Specific animation for transition 2. Default animation for source state 3. Default animation for target state 4. Default animation
| * | Add tests for the removeDefaultAnimation* APIEskil Abrahamsen Blomfeldt2009-04-221-0/+127
| | |
| * | Add API for adding default animations to the state machine. This is especiallyEskil Abrahamsen Blomfeldt2009-04-214-4/+272
| | | | | | | | | | | | | | | | | | | | | useful when using the RestoreProperties policy, because this is intended to allow you to build a state machine without having each state consider all the possible properties that may be set by some state at some point. Default animations provide the same convenience for animated properties.
| * | QAnimationState is no more, so we remove the test for it. The relevant testsEskil Abrahamsen Blomfeldt2009-04-213-630/+327
| | | | | | | | | | | | have been ported to the new API and added to the QStateMachine autotest instead.
| * | doc: Document return value of QState::addTransition(QAbstractTransition*)Eskil Abrahamsen Blomfeldt2009-04-211-1/+2
| | |
| * | Have QState::addTransition(QAbstractTransition*) return the transition objectEskil Abrahamsen Blomfeldt2009-04-212-5/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | when it is added. Reduces the number of temporary variables you have to declare in your code since you can do things like: state->addTransition(new Transition())->addAnimation(new Animation()); Could also be used for error checking.
| * | compile.Eskil Abrahamsen Blomfeldt2009-04-211-3/+3
| | |
* | | Fix a bug in the ease{In,Out}Bounce easing functions + small cleanup.Jan-Arve Sæther2009-04-232-109/+108
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The bug was in easeOutBounce_helper(), where the last else-block adjusted t wrong. It should adjust t so that the peak is at t == 0, but it adjusted it too little. The old code did t -= (2.25f/2.75f), but it should have been 21/22. The rest of the changes in that function is just simple mathematical rewrites (use a more readable fraction), and removed the b argument, since that was always 0. Finally, fixing the original bug also revealed a bug in the first line of easeOutBounce_helper(), where we always returned 1.0 for t == 1.0. That was wrong since it did not respect c.
* | | Remove trailing whitespaceJan-Arve Sæther2009-04-231-8/+8
| | |
* | | Remove trailing whitespaceJan-Arve Sæther2009-04-231-32/+32
| | |
* | | Moved the animation examples piemenu and photobrowser to examples/researchLeonardo Sobral Cunha2009-04-2316-0/+0
| | |
* | | Update copyright headers of animation examplesLeonardo Sobral Cunha2009-04-2354-110/+1937
| | |
* | | Fixes QPropertyAnimation's default start value update conditionLeonardo Sobral Cunha2009-04-223-20/+38
| | | | | | | | | | | | | | | | | | | | | The default start value is updated when the animation changes from Stopped to Running state. Reviewed-by: Jan-Arve
* | | Fixes for solution package.Jan-Arve Sæther2009-04-227-54/+89
| | |
* | | Expose QVariantAnimationPrivate::getInterpolator in the private headerLeonardo Sobral Cunha2009-04-212-2/+4
| | | | | | | | | | | | These interpolator functions might be useful for other internal classes.
* | | QPropertyAnimation reevaluates the default start value after each runLeonardo Sobral Cunha2009-04-213-7/+41
| |/ |/| | | | | | | | | | | | | When the start value is not explicitly defined, the property animation will set the default start to be the current property value when updating the animation's state to Running. Reviewed-by: Jan-Arve
* | update the package script according to class renamingKent Hansen2009-04-211-4/+4
|/
* Merge branch 'kinetic-animations' into kinetic-statemachineKent Hansen2009-04-212-1/+36
|\
| * Fixes bug when adding the same child animation twice to the same groupLeonardo Sobral Cunha2009-04-212-1/+36
| | | | | | | | | | | | | | | | The child animation was removed twice from the group because in QAnimationGroup::insertAnimationAt the insertion in the list was done before removing the animation. Reviewed-by: Jan-Arve
generated by cgit v0.12 at 2024-11-26 04:28:01 (GMT)