summaryrefslogtreecommitdiffstats
path: root/examples
Commit message (Collapse)AuthorAgeFilesLines
* Fix top level compile in examples/animationEskil Abrahamsen Blomfeldt2009-05-141-3/+0
| | | | Three examples have been moved.
* Make QAbstractTransition::eventTest() non-constEskil Abrahamsen Blomfeldt2009-05-1410-22/+22
| | | | | We decided to remove the const of the eventTest() since some transitions have dynamic conditions and need to update when eventTest() is called.
* Pop up message when a tank wins the gameEskil Abrahamsen Blomfeldt2009-05-147-12/+111
| | | | | Also fixed: Added some docs and moved the tanks a little so they don't start partly outside the scene rect.
* Fix run-time error in Seek AI's state machineEskil Abrahamsen Blomfeldt2009-05-141-1/+5
| | | | | Passed parent as 'tank', thus getting a null parent in the GoToLocation state, which breaks the machine when you transition into the state.
* Fix SpinState in Tank Game Example to spin more than 180 degreesEskil Abrahamsen Blomfeldt2009-05-142-2/+12
| | | | This was a leftover from when the setDirection() semantics were broken.
* document statemachine/factorial exampleKent Hansen2009-05-131-26/+38
|
* doc: Correct names of snippets in docs for Tank Game exampleEskil Abrahamsen Blomfeldt2009-05-131-0/+4
|
* document the statemachine/eventtransitions exampleKent Hansen2009-05-121-1/+15
|
* Change name of "errorstate" example to "tankgame"Eskil Abrahamsen Blomfeldt2009-05-1226-29/+40
| | | | | The error state is not a big enough part of the example to justify naming it after it.
* Fixes: document statemachine/twowaybutton exampleKent Hansen2009-05-121-7/+15
|
* kill some simplistic/overlapping/under-developed examplesKent Hansen2009-05-129-445/+0
|
* document the statemachine/pingpong exampleKent Hansen2009-05-121-0/+14
|
* Merge branch 'kinetic-statemachine' of git@scm.dev.nokia.troll.no:qt/kinetic ↵Alexis Menard2009-05-12120-763/+4176
|\ | | | | | | | | | | | | into kinetic-statemachine Conflicts: src/gui/graphicsview/qgraphicsitem.cpp
| * improve the docs for the trafficlight exampleKent Hansen2009-05-121-25/+22
| |
| * Make selecting plugins more user friendly and platform independentEskil Abrahamsen Blomfeldt2009-05-115-18/+66
| | | | | | | | | | | | Using *.dll was just a placeholder here. The code is mostly copied from the Plug&Paint example, and goes through all the plugins to find the compatible ones with some hacks to find out the application directory on windows and mac.
| * Instead of adding animations for all properties to all transitions, we useEskil Abrahamsen Blomfeldt2009-05-061-7/+11
| | | | | | | | the default animation concept, since this is its intended use.
| * Add chase state and ability to detect and fire at other tanks. This reveals anEskil Abrahamsen Blomfeldt2009-05-062-4/+92
| | | | | | | | assert in the state machine which needs to be debugged.
| * Avoid passage where the walls meet the edge of the scene rect.Eskil Abrahamsen Blomfeldt2009-05-061-5/+6
| |
| * get rid of marginKent Hansen2009-05-051-1/+2
| |
| * add event as argument to onEntry(), onExit() and onTransition()Kent Hansen2009-05-0515-50/+50
| | | | | | | | | | | | | | | | | | 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.
| * Add randomness.Eskil Abrahamsen Blomfeldt2009-05-051-2/+2
| |
| * Make sure target state is set correctly. Also make sure eventTest() actuallyEskil Abrahamsen Blomfeldt2009-05-051-5/+8
| | | | | | | | overrides the virtual function.
| * Set collidedLine for the implicit walls around the scene to allow for collisionEskil Abrahamsen Blomfeldt2009-05-051-4/+21
| | | | | | | | response.
| * Make sure the correct position/direction is actually set at the end of aEskil Abrahamsen Blomfeldt2009-05-051-10/+16
| | | | | | | | loop. Also make sure we set the direction to an angle within 360 degrees.
| * Fix support reverse actions. Logic was broken and would always return falseEskil Abrahamsen Blomfeldt2009-05-051-2/+2
| | | | | | | | immediately for reverse actions, thus immediately stopping them.
| * Add unfinished "more advanced" AI for errorstate.Eskil Abrahamsen Blomfeldt2009-04-306-5/+184
| |
| * Make design better. Remove the Tank interface. This is now an implicit interfaceEskil Abrahamsen Blomfeldt2009-04-3016-86/+65
| | | | | | | | based on the meta-object system.
| * Add two AIs: They are both designed to do the same. Spin until they see a tankEskil Abrahamsen Blomfeldt2009-04-3014-26/+262
| | | | | | | | | | | | 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.
| * kill QStateMachine::animationsFinished(), introduce QState::polished()Kent Hansen2009-04-291-2/+2
| |
| * Compile against new QState::ChildMode API.Eskil Abrahamsen Blomfeldt2009-04-291-1/+1
| |
| * Kill gameOver signal as it was only used when you clicked the stop actionEskil Abrahamsen Blomfeldt2009-04-292-9/+6
| |
| * Merge branch 'kinetic-animations' into kinetic-statemachineKent Hansen2009-04-2921-117/+370
| |\ | | | | | | | | | | | | Conflicts: examples/animation/sub-attaq/states.cpp
| | * Build fix for mingwThierry Bastian2009-04-2718-54/+52
| | |
| | * Add an OSD to display game progress in the sceneAlexis Menard2009-04-2411-65/+320
| | |
| * | replace QState::Type with QState::childMode propertyKent Hansen2009-04-292-2/+2
| | | | | | | | | | | | Result of API review.
| * | Adapt to recent API changes and bug fixes.Eskil Abrahamsen Blomfeldt2009-04-291-2/+6
| | |
| * | modifiers --> modifiersMaskKent Hansen2009-04-291-9/+0
| | | | | | | | | | | | | | | | | | 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.
| * | make history state constructibleKent Hansen2009-04-292-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-292-37/+18
| | | | | | | | | | | | It's useful and it's simple for us to expose, so let's.
| * | 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.)
| * | 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().
| * | compile after api changesKent Hansen2009-04-283-8/+8
| | |
| * | 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-248-27/+12
| |\ | | | | | | | | | | | | Conflicts: examples/animation/piemenu/qgraphicspiemenu_p.h
| | * Remove API for setting specific restore policies on states. We have no clearEskil Abrahamsen Blomfeldt2009-04-231-1/+1
| | | | | | | | | | | | | | | | | | 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-225-11/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | Moved the animation examples piemenu and photobrowser to examples/researchLeonardo Sobral Cunha2009-04-2316-0/+0
| | |
generated by cgit v0.12 at 2024-12-28 03:37:52 (GMT)