| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Rationale: We're using template magic now to get the private
pointer in qglobal.h, so no need to have two macros. Also
keeps backward compatibility with outside (KDE) code.
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/corelib/global/qglobal.h
src/corelib/kernel/qmetatype.cpp
src/corelib/kernel/qobject.cpp
src/corelib/thread/qthread_unix.cpp
src/gui/graphicsview/qgraphicssceneevent.h
src/gui/itemviews/qheaderview.h
src/gui/kernel/qapplication_qws.cpp
src/gui/kernel/qgesture.h
src/gui/kernel/qgesturerecognizer.h
src/gui/painting/qpaintengine_raster.cpp
src/network/access/qhttpnetworkreply.cpp
src/network/access/qnetworkcookie.h
src/network/socket/qnativesocketengine_unix.cpp
|
| | |
| |
| |
| |
| | |
Contains some smaller fixes and renaming of macros. Looks big,
but isn't scary at all ;)
|
| |/
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
QT_NO_DRAGANDROP
QT_NO_ACTION
QT_NO_GRAPHICSVIEW
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: Thierry Bastian
|
| |
|
|
| |
There should be no QT_{BEGIN,END}_HEADER here; this is a private header.
|
| |
|
|
| |
Copy&paste error; the classes are in Gui, not Core.
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| | |
|
| |\ |
|
| | |\
| | |
| | |
| | | |
into kinetic-animations
|
| | |\ \
| | | |
| | | |
| | | | |
into kinetic-animations
|
| | | | | |
|
| | |_|/
|/| |
| | |
| | |
| | | |
We decided to remove the const of the eventTest() since some transitions
have dynamic conditions and need to update when eventTest() is called.
|
| | |/
|/|
| |
| | |
We won't release another Qt Solution, so the define is no longer needed.
|
| |/
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
