Qt.git - Qt s a cross-platform application framework that is used for developing application software that can be run on various software and hardware platforms with little or no change in the underlying codebase, while still being a native application with native capabilities and speed.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Make QSignalEvent and QWrappedEvent inner classes of QStateMachine	Kent Hansen	2009-09-28	1	-3/+1
\| \| \| \| \| \| \| \| \|	Those two classes are specific to the state machine framework, but their names were so generic that we felt they were polluting the Q-namespace. They are now QStateMachine::SignalEvent and QStateMachine::WrappedEvent. Reviewed-by: Eskil Abrahamsen Blomfeldt
*	rename QBoundEvent to QWrappedEvent and make it public	Kent Hansen	2009-04-29	1	-1/+1
\| \| \| \|	Result of API review.
*	replace QStateFinished{Event,Transition} by QState::finished() signal	Kent Hansen	2009-04-27	1	-3/+0
\| \| \| \| \|	Not worth it having two public classes when the same can be achieved by having a signal.
*	kill the stateactions api	Kent Hansen	2009-04-22	1	-9/+0
\| \| \| \| \| \| \| \| \| \| \| \|	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.
*	rename QTransition -> QActionTransition	Kent Hansen	2009-04-21	1	-3/+3
\|
*	Initial import of statemachine branch from the old kinetic repository	Alexis Menard	2009-04-17	1	-0/+42