| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Since there is more than one standard shorcut for closing a MDI window,
then ensure that all of them can be used.
Task-number: 161999
Reviewed-by: Simon Hausmann
|
| |
|
|
|
|
|
|
| |
Regression since my last commit.
Task-number: 152227
|
|
|
|
|
|
|
| |
This is also a work around for a bug in gcc on powerpc (embedded-linux)
Task-number: 258358
Reviewed-by: jbache
|
| |
|
|
|
|
| |
The base function was \internal pr private.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We need this to support the behavior in Gtk+ where, when
Qt::ToolButtonTextBesideIcon is used, only text labels
for important actions are shown. It will also enable us to
prioritize actions in the future when for instance collapsing
a toolbar.
Task-number: 258290
Reviewed-by: thierry
|
|
|
|
|
|
|
|
|
|
|
|
| |
KDE and GNOME has the concept of a default tool button style that
can be set system-wide. Qt currently allways default to IconOnly.
I have added an optional Qt::ToolButtonSystemDefault value so you
can opt-in to respect the system setting. We did not change the
default because a lot of apps will look odd when for instance
text is beside icons and the descriptive text is too long.
Task-number: 237864
Reviewed-by: ogoffart
|
| |
|
|
|
|
|
|
|
|
| |
Qt::TextShowMnemonic removes the '&' for us.
This is required if we want the multi-lenght-variant strings working.
Reviewed-by: Thierry
|
|
|
|
|
|
|
| |
Found while documenting this internally.
I guess I had a reason for it at one point, but it
seems that I'm more concerned about what index. So
just get rid of this.
|
|
|
|
|
|
| |
These functions hide all this horrible casting and
we've had them for a while. When I see them, I try
to replace them as it keeps the code much more readable.
|
|
|
|
|
| |
we should include qt_windows.h and not windows.h because we have to
define WINVER to 0x500.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This has always been a bit bumpy, the problem is that the popup normally
has its own styling from the desktop, plus it's its own top-level and
that is normally a boundary for propagation. Of course, people are
surprised by this (especially when it works for editable). So, we need
to be a bit better propagating the info. Also the QStyleOptionMenuItem
has the correct font, but if it's set on a window, by the time it
reaches the popup, its resolve mask is very weak, so it will fail to
resolve at all. Setting the point size allows the font to have a bit of
strength.
Task-number: 257486
Reviewed-by: Jens Bache-Wiig
|
|
|
|
|
|
|
|
|
|
|
| |
NT support"
tst_QGraphicsProxyWidget crashed because the QAlphaWidget tried to access a
deleted widget. Before we had the if check, but that was removed
with this commit: 55137901. Completely wrong, we must check the widget pointer
before using it.
Reviewed-by: jbache
|
| |
|
|
|
|
| |
The layoutState is already current (ie. already applied).
|
|
|
|
|
|
| |
Maximum number of decimals is DBL_MAX_10_EXP + DBL_DIG
Task-number: 257291
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Basically if you would hide a toolbar in the unified toolbar, you
would still see a little bit of area at the top instead of having
everything flush with the titlebar. This change basically unsures that
the unified toolbar makes a decision to hide itself if all the toolbars
inside it are hidden. It makes the behavior of clicking on the toolbar
button behave more or less correctly since we are going to show the
unified toolbar whether we want to or not.
This all will get the toolbar button switch event to be dispatched in
Cocoa as well.
Also add an optimization for checking if we need to change the geometry.
If we don't have any items the other toolbar areas, we can skip the set
geometry call, which wrecks havoc with things in Cocoa.
We still don't solve the case of someone who has hidden the items with
the toolbar button then goes full-screen, then goes back out. I'm not
motivated to solve it as is because we need to keep track of the
hides we do on the button press vs. other hides from the user and still
people can workaround it easy enough by handling window state change and
doing what is recommended in the docs.
Task-number: 208439
Rev-by: Denis
|
|
|
|
| |
Reviewed-by: Thierry
|
|
|
|
| |
QTimeLine is now no more used in private APIs
|
|
|
|
|
| |
Triggered on Designer startup on Linux.
Acked-by: Thierry Bastian <thierry.bastian@nokia.com>
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/sql/drivers/ibase/qsql_ibase.cpp
tests/auto/q3sqlcursor/tst_q3sqlcursor.cpp
tests/auto/qsqldatabase/tst_databases.h
tests/auto/qsqldatabase/tst_qsqldatabase.cpp
translations/qt_ru.ts
|
| |
| |
| |
| |
| |
| |
| |
| | |
We cannot assume the position of the decorations when a QGroupBox get
the focus.
Task-number: 257660
Reviewed-by: Thierry
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
If you had invisible actions in the menubar, it would always show the
extension button
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
This happened because the rubberband used as a gapindicator was not
allocated on the heap and might have been deleted by the QMainWindow
destructor.
Task-number: 257626
|
| |
| |
| |
| | |
This required some refactoring as well. Now code is leaner and cleaner
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a crashed introduced in
60e965fd35037f4a27816d2aeccafdff0d6ae9d6 - those lines were removed by
accident.
Reviewed-by: João Abecasis
Author: João Abecasis
|
| |
| |
| |
| | |
Task-number: 246999
|
| |
| |
| |
| | |
using const references to pass parameter
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Unfortunately the codepath for keyPressEvent does not call updateState,
so we have to add the same line in two places.
Note that updateState() is only called from mousePressEvent() and
mouseMoveEvent().
Task-number: 254053
|
| |
| |
| |
| | |
sizeHint is now fixed
|
| |
| |
| |
| |
| |
| |
| | |
The toolbar that one would unhide could be packed at the right of the
screen. This was because the last toolbar always has a size that fills
the space. So if you unhide a toolbar situated after this one, it got
"compressed".
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Setting the current font would change the current font and then it
would try to select the right model index and get the font only from
the text of the combobox. This was resetting the point size of the font,
resulting in emitting the signal a second time.
In the case of the user, it was also causing signals to be called in
a loop.
Task-number: 229731
|
| |
| |
| |
| | |
Task-number: 257118
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
On Mac OS X, QMenuBar::clear() does not remove menu items
that have been merged into the system menu bar.
Task-number: 255222
|
| |
| |
| |
| |
| |
| | |
HoverEnter/Leave now do nothing.
Task-number: 256103
|
| |
| |
| |
| |
| | |
With document margins, the mapping from content-coordinates to visual
coordinates went wrong.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rewritten the api almost from scratch, making it simplier and more
flexible at the same time.
The current implementation will not have complex gseturemanager class
inside Qt, but the QGesture base class, which represents both a
gesture recognizer and a gesture itself with a set of properties. A
set of common gestures that can use used in third-party applications
(and in Qt itself internally) is supposed to be found in
qstandardgestures.h, and a base class for user-defined gestures is in
qgesture.h
Gesture implementation for Pan on Windows7 has also been added as a
reference implementation for platform gestures.
|
| |
| |
| |
| |
| |
| |
| |
| | |
For example when an unhandled key sequence (i.e. that has now shortcut
assosiated with it) like Alt-L is pressed, we shouldn't insert the 'L'
text from the QKeyEvent::text() into the text widget.
Reviewed-by: Thomas Zander
|
|\ \
| |/ |
|
| | |
|
| | |
|