| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Reviewed-by: Trust Me
|
|\ |
|
| |
| |
| |
| | |
Reviewed-by: Richard
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
QPrintPreviewWidget wasn't following the Qt API naming convention of
*Count()/set*Count(). Introduce proper function, and obsolete the old.
Removed all usage of the old function in Qt.
Reviewed-by: Andreas Aardal Hanssen
|
| |
| |
| |
| |
| |
| |
| | |
QLCDNumber doesn't follow the API convention of *Count and set*Count().
Introduce properly named functions, and obsolete the old ones.
Reviewed-by: Andreas Aardal Hanssen
|
| |
| |
| |
| |
| |
| |
| | |
We added the class QMargins, so we should use it wherever we deal with
margins, as a convenience to the users.
Reviewed-by: Andreas Aardal Hanssen
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
dist/changes-4.6.0
|
| |/
| |
| |
| | |
Reviewed-by: tom
|
| |
| |
| |
| | |
Reviewed-by: Thierry
|
|\ \
| |/ |
|
| |\
| | |
| | |
| | |
| | |
| | | |
Conflicts:
dist/changes-4.6.0
src/gui/kernel/qevent.h
|
| | |
| | |
| | |
| | |
| | |
| | | |
Changes to the gesture api after the review.
Reviewed-by: Jasmin Blanchette
|
| | |
| | |
| | |
| | | |
Reviewed-by: trustme
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously we didn't update the editor contents if the new preedit
string was empty. However, it could be empty because the user just
erased it, so the bug was fixed by checking whether the preedit
string in the event and in the editor are different.
RevBy: Denis Dzyubenko
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the QWidgetAction is not the first in a menu, it crashed.
This is because when the QEvent::ActionRemoved is sent, the
event->before() is not set. We need to find another way to
clean up the widgetItems list.
This basically revert 4b6ab00e6d68c7
Reviewed-by: Thierry
|
|\ \ \
| |/ / |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: tom
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: tom
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
However, compiling with QT_NO_ICON will still not work :(
Reviewed-by: tom
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: tom
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: tom
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When echo mode was set to PasswordEchoOnEdit in a QLineEdit, and its text
selected, pressing the return key would erase the text and start editing it
instead of validating the password. Auto-test included.
Reviewed-by: Olivier
Task-number: QTBUG-4401
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Task-number: QTBUG-1071
Reviewed-by: ogoffart
|
|\ \ \ \
| | |/ /
| |/| | |
|
| |\ \ \
| | | |/
| | |/| |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This also adds QStyleOptionTabWidgetFrameV2 so that we do not have
to do ugly hacks in the style to obtain it.
Task-number: QTBUG-5187
Reviewed-by: ogoffart
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
While drawing the tabbar frame, mac style needs the QTabBar pointer to
calculate the correct size.
Since the QTabWidget also uses the PE_FrameTabBarBase to draw background
of the corner widgets, the mac style has to use position passed with the
style option. This only works with horizontal tabs.
Reviewed-by: Jens Bache-Wiig
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Dragging is handled by a seperate window in document mode. The currently
selected tabbar item is drawn to a pixmap for this purpose. That
paintdevice was not initialized correctly. (e.g. font)
Reviewed-by: Trond
|
| | |\ \
| | | |/
| | |/|
| | | | |
4.6-WM_NULL-driven
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When a tab is clicked and mouse is moved outside that tab, it should
be drawn as normal (not in sunken state).
Reviewed-by: MortenS
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We used to not start an animation of the current geometry was already
set. The problem is that starting this animation might stop another
animation. This has to happen. Otherwise subsequent calls to animate
a widget might or might not be executed.
Reviewed-by: ogoffart
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
popup
The problem is that is we move the selection with the keyboard
in a way that causes the view to scroll, the current selection
would jump.
This happends since commit 9cb231d773db6deb that fixed the emission
of the enter signal when the view is scrolled.
We Therefor cannot use the enter signal. Catch manually the mouse
move events to update the selection instead.
Reviewed-by: Thierry
|
| | | |
|
|\ \ \
| |/ / |
|
| |\ \ |
|
| | |\ \
| | | |/ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The created keyed actions are passed to wrong widget if this pointer
is passed insted of itemView. Also create softkey actions in
setItemView method instead of constructor in order that custom items
views are also working correctly.
Task-number:: QTBUG-4702
AutoTest: All QComboBox tests passed
Reviewed-by: Jason Barron
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
At the moment, Qt, in many places, does not really understand that
a mouse wheel, or touch pad, might operate on a much higher
granularity than 15 degrees (that is, a delta of 120). This is clear
disadvantage on mac, since the mighty mouse, and track pad, got a
resolution that is close to 1 degree. This is called pixel scrolling.
This patch first and formost changes the implementation of
QAbstractSlider::wheelEvent to _really_ understand what to do when
delta is less than 120. Rather than accumulate delta until 120
is reached, then scroll with a value equal to:
offset * step * QApplication::wheelScrollLines (default = 3), we
multiply offset directly, before waiting for 120. This means that
event tough offset is below 120, multiplying it with wheelScrollLines
and step will very often give a value over 120, menaing we can scroll
much earlier and _much more_ fined grained. This also fixes some
auto tests that was ifdeffed out because of specialised mac code
written inside this function from before.
(NB: we still plan to introduce a new event for pixel scrolling,
perhaps for Qt-4.7)
Rev-By: Andreas
Rev-By: denis
|
| | |
| | |
| | |
| | | |
Task-number: QTBUG-1171
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If it wasn't already docked on a mainwindow, its state would become
unexpected.
Task-number: QTBUG-945
Reviewed-by: gabi
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
After deleting or hiding the last non collapsed item in a QSplitter, none would
be visible. We now check wether there is any non-hidden, collapsed widget, and
set it to non-collapsed. Auto-test included.
Task-number: QTBUG-4101
Reviewed-by: Olivier
|
|\ \ \ \
| |/ / /
|/| / /
| |/ /
| | |
| | |
| | |
| | | |
git://gitorious.org/~fleury/qt/fleury-openbossa-clone into openbossa-fleury-fixes3
Conflicts:
src/gui/graphicsview/qgraphicsanchorlayout_p.cpp
src/gui/graphicsview/qgraphicsanchorlayout_p.h
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
QTextEdit (via QTextLayout) and QPlainTextEdit in Qt used to ignore
any font leading but added one extra pixel in QFontMetrics. With many
freetype fonts, this resulted in a "spacy" text layout.
The necessary fixes on X11 and Windows were to take (positive) leading
into account, to make the font database convert point sizes to pixel
sizes without rounding to plain integer values, and to subtract the
extra pixel from QFontMetrics from the font engines' descent value.
The change also fixes several places in styles and widgets, where
QFontMetrics::lineSpacing() was wrongly used instead of
QFontMetrics::height().
Ideally we should also handle negative leading, which would require
additional and bigger code changes in QTextLayout and QPlainTextEdit.
In addition, all other editors we have tested seem to ignore leading on
X11. If we choose to believe the values provided by freetype, our text
layout would be one pixel smaller than everybody else's.
On the Mac, this change does nothing. There our layout is still too spacy,
and for smaller fonts quite ugly compared to native Mac applications.
Done with mae.
Reviewed-by: mae
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
setReadOnly.
Should set Qt::WA_InputMethodEnabled after set the flags, just because shouldEnableInputMethod() will read the flags.
Task-number: QTBUG-4917
Reviewed-by: Shane Kearns
|
| |
| |
| |
| |
| | |
Task-number: QTBUG-4169
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| | |
Task-number: QTBUG-569
Reviewed-by: ogoffart
|