| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
bin/syncqt
doc/src/deployment/deployment.qdoc
src/corelib/io/qfsfileengine_win.cpp
src/corelib/xml/qxmlstream.cpp
src/opengl/gl2paintengineex/qpaintengineex_opengl2_p.h
tools/assistant/tools/assistant/centralwidget.cpp
tools/linguist/lupdate/main.cpp
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
Reviewed-by: Trust Me
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When creating a single dialog in the main function, and tell it
to exec, we run a modal dialog. But there is really no other
window on screen to be modal for. So in that case, since this is
a rather common pattern for Qt applications, we allow users to
quit the application from the dock. But this action is sendt as
an apple event. And and that point in time, cocoa has the the
apple event handler, and refuses to close down the application
because it detects a modal window.
Our solution is to install/overwrite the apple event handler for
kAEQuit _after_ cocoa has finished its own installation. But in
order to do this, we need to wait until [NSApplication run] has
started, otherwise it will not take effect. And that is what this
patch essentially does.
|
| |/
|
|
| |
Task-number: QTBUG-6474
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: tom
|
| |
|
|
| |
Reviewed-by: Harald Fernengel <harald.fernengel@nokia.com>
|
| |
|
|
| |
Reviewed-by: tom
|
| |
|
|
| |
Reviewed-by: paul
|
| |
|
|
| |
Reviewed-by: tom
|
| |
|
|
|
|
| |
Make it clearer what the property actually does.
Reviewed-by: Kent Hansen
|
| |
|
|
|
|
| |
"modifierMask" is more correct English.
Reviewed-by: Kent Hansen
|
| |
|
|
| |
Reviewed-by: thartman
|
| |
|
|
|
| |
Now using QEventTransition with almost any type of event will
actually work, instead of causing an assert.
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
