summaryrefslogtreecommitdiffstats
path: root/examples/animation
Commit message (Collapse)AuthorAgeFilesLines
* Update contact URL in license headers.Jason McDonald2009-08-1219-19/+19
| | | | Reviewed-by: Trust Me
* remove constructors that are not usefulKent Hansen2009-08-031-2/+4
| | | | | | | The constructors that take a list of target states produce hard-to-read code, and they're rarely useful in practice since 99% of transitions take a single target state; so it's better to enforce that setTarget{State,States}() be used instead.
* Move sub-attaq from examples to demos because sub-attaq is a bitAlexis Menard2009-07-2872-6521/+0
| | | | too "advanced".
* Make QStateMachine inherit QStateKent Hansen2009-07-2210-32/+29
| | | | | | | | | | | | | | | | | | This removes the need for a "root state" in the machine; or rather, the machine _is_ the root state. User code can now pass in a QStateMachine directly to the QState constructor, instead of machine->rootState(). This also means we could get rid of the "proxying" from the machine to the root state for things like properties (initialState et al), finished() signal and auto-reparenting of states (the ChildAdded event hack). A fun little side-effect of this change is that it's now possible to embed state machines within state machines. We can't think of a good use case yet where you would rather embed a stand-alone state machine (with its own event processing etc.) rather than having just a regular nested state, but it's neat and it works. Reviewed-by: Eskil Abrahamsen Blomfeldt
* Remove Stickman editorEskil Abrahamsen Blomfeldt2009-07-217-437/+0
| | | | | The editor was a just a detail to make the animations and shouldn't be included in the example.
* Animation: fixed a NOTIFY signal name that was wrongThierry Bastian2009-07-011-6/+6
| | | | Also slightly updated a demo
* Doc: Documented the Move Blocks example.Geir Vattekar2009-06-291-4/+32
| | | | Reviewed-by: Andreas Aardal Hanssen
* Update license headers in files that are new in 4.6.Jason McDonald2009-06-1750-100/+100
| | | | Reviewed-by: Trust Me
* Make sure we draw the complete curve.Jan-Arve Sæther2009-06-081-1/+1
|
* Use a QPainterPath instead to draw the graph.Jan-Arve Sæther2009-06-081-5/+5
| | | | | | This enables the antialiazing to be done on the graph as a whole, and not on every tiny line segment. The result is that the curve is painter prettier.
* Remove trailing whitespace.Jan-Arve Sæther2009-06-081-7/+7
|
* Make the easing curve icons more beautiful.Ariya Hidayat2009-06-081-3/+17
| | | | | | | | Draw the curve with anti-aliasing. Do not use absolute black, but rather a dark black color for the lines. Draw the red and blue dots, indicating the start and end points. Reviewed-by: Jan-Arve
* Fixed compile error with Sun CC 5.5.jasplin2009-06-051-1/+1
| | | | Reviewed-by: TrustMe
* Fixed sub-attaq example buildThiago Marcos P. Santos2009-05-291-0/+2
|
* Fix build when compiling Qt using -no-opengl configuration.Brad Hards2009-05-281-3/+6
|
* small cleanup on the sub-attaq demoThierry Bastian2009-05-286-9/+6
| | | | removed declaration of properties that are already declared in Qt
* Fixes sub-attaq in shadow build.Olivier Goffart2009-05-272-1/+2
| | | | Reviewed-by: Alexis
* Compile without OpenGLOlivier Goffart2009-05-271-3/+3
| | | | Reviewed-by: Alexis
* Removed some export to symbols that don't need itThierry Bastian2009-05-252-35/+14
| | | | ...hopefully
* Make sure M_PI is definedKent Hansen2009-05-221-0/+4
| | | | It isn't on all platforms.
* Don't use the time() function; use QTime insteadKent Hansen2009-05-221-2/+1
| | | | time() is not available on all platforms.
* Fix compile issueThierry Bastian2009-05-221-0/+2
| | | | Reviewed-by: Kent Hansen
* Fix compile error caused by reference to non-existant example.Jason McDonald2009-05-211-1/+0
| | | | Reviewed-by: Trust Me
* Fix missing/outdated license headers.Jason McDonald2009-05-212-2/+24
| | | | Reviewed-by: Trust Me
* update the padnavigator example and suppress the padnavigator-ngThierry Bastian2009-05-2019-982/+0
|
* fix compiler warningsKent Hansen2009-05-202-3/+3
|
* fix two .pro file bugsKent Hansen2009-05-201-1/+0
|
* compile with -qtnamespace, clean up the example .pro filesKent Hansen2009-05-2023-59/+78
|
* add README file for examples/animationKent Hansen2009-05-201-0/+38
|
* Remove old examples and demos for animationsThierry Bastian2009-05-2032-3078/+0
|
* Removing QT_EXPERIMENTAL_SOLUTION from the animation apiLeonardo Sobral Cunha2009-05-1927-174/+14
|
* Remove the connectByAnimation() function and add some documentation for the ↵Eskil Abrahamsen Blomfeldt2009-05-142-28/+22
| | | | | | | Stickman example The connectByAnimation() function is no longer needed since we have default animations. The docs are unfinished.
* Start work on docs for Stickman exampleEskil Abrahamsen Blomfeldt2009-05-141-3/+5
|
* 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-145-12/+12
| | | | | We decided to remove the const of the eventTest() since some transitions have dynamic conditions and need to update when eventTest() is called.
* 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 event as argument to onEntry(), onExit() and onTransition()Kent Hansen2009-05-057-34/+34
| | | | | | | | | 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.
* kill QStateMachine::animationsFinished(), introduce QState::polished()Kent Hansen2009-04-291-2/+2
|
* 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
| |
* | 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-291-1/+1
| | | | | | | | | | | | | | | | | | | | | | 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.
* | compile after api changesKent Hansen2009-04-281-2/+2
|/
* Merge branch 'kinetic-statemachine' into kinetic-animationsKent Hansen2009-04-246-22/+7
|\ | | | | | | | | 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-223-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | 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 2025-01-04 11:31:13 (GMT)