| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fixes: QTBUG-5146
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
QPaintDevice and QImage used the functions numColors(), setNumColors(),
and numBytes(). However, this is not consistent with the rest of the Qt
API which uses *Count() and set*Count().
Removed all usage of these functions inside Qt and test-cases.
Reviewed-by: Andreas Aardal Hanssen
|
|\ \
| |/ |
|
| |\ |
|
| | |
| | |
| | |
| | | |
RevBy: Trust me
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
QAbstractAnimation:
currentTime returns the "complete" current time
currentLoopTime() returns the time inside the current loop
add setPaused(bool) for consistency with QTimeLine
stateChanged: newState passed as first paramater (before oldState)
for consistency with the reset of Qt
QAnimationGroup:
rename clearAnimations to clear
rename insertAnimationAt to insertAnimation
rename takeAnimationAt to takeAnimation
QSequentialAnimationGroup:
rename insertPauseAt to insertPause
|
|\ \ \
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The QGtk class has been refactored into a private d class for QGtkStyle.
This allows us to re-use a lot of code for the Maemo5 style without changing
a single line in QGtkStyle itself plus we can easily add virtual functions
where the two styles need to behave different.
There shouldn't be any new functionality added (or old functionality lost) by
this commit.
Reviewed-By: jbache
Reviewed-By: Ralf Engels
|
| |\ \
| | |/
| |/|
| | |
| | |
| | | |
Conflicts:
src/gui/kernel/qevent.cpp
src/network/ssl/qsslerror.cpp
|
| | |
| | |
| | |
| | | |
Reviewed-by: Oswald Buddenhagen
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The spacing was not being substracted from the viewport width when calculating
the available space for items. Auto-test included.
Reviewed-by: Olivier
Task-number: QTBUG-2678
|
|/ /
| |
| |
| |
| | |
Task-number: QTBUG-5007
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| |
| |
| |
| | |
The lasts commits in the treeview did put the flags weither
item has child or is the last in cache in the viewItem vector.
But the cache was not updated while the model is modified.
Reviewed-by: Thierry
|
| |
| |
| |
| |
| | |
Task-number: QTBUG-560
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| | |
Task-number: QTBUG-435
Reviewed-by: Gabriel
|
| |
| |
| |
| |
| | |
Task-number: QTBUG-633
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| |
| |
| | |
autotest included
Task-number: QT-711
Reviewed-by: ogoffart
|
| |
| |
| |
| | |
Reviewed-by: andreas
|
| |
| |
| |
| |
| |
| |
| |
| | |
In some cases, the spans internal structure was left in an inconsistent
state. Auto-test included. Bonus: spans consistency checking method.
Task-number: QTBUG-5062
Reviewed-by: Olivier
|
| |
| |
| |
| |
| |
| |
| | |
..from the decoration to the item itself. QAbstractItemView can't
handle that because it doesn't know anything about decoration.
Reviewed-by: gabi
|
|\ \
| |/
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| | |
As noticed by Laurent Montel.
Merge-request: 1812
Reviewed-by: Olivier Goffart <ogoffart@trolltech.com>
|
| |
| |
| |
| |
| | |
Task-number: QTBUG-976
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| |
| |
| |
| | |
That state used not to be set for drawing the content of the items.
Also, it could be wrong for branches if there was hidden items.
Reviewed-by: Thierry
Task-number: related to 234930
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
the ::item pseudo-class
The State_Children was not set on the QStyleOption.
Refactorized a little bit the way it was computed.
Reviewed-by: Thierry
Task-number: 234930
Task-number: QTBUG-3129
|
| |
| |
| |
| |
| |
| |
| |
| | |
The problem was that we didn't call ensurePolished when getting the
size of the sections.
Task-number: QTBUG-1002
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| |
| |
| | |
Would not have introduced any bug as invald QModelIndex are currently
initialised with -1 for row and column.
Reviewed-by: trust me
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now, when dropping items, these will remain selected, and in the same visual
order as when dragged.
Auto-test included for the items moving part. For the rest, it's a
drag-and-drop thing.
Reviewed-by: Olivier
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Extended the behaviour already present in QAbstractItemView into
QListView. This means some code duplication which should maybe be refactored
at some point. (Seems to be the price to pay when some delegate does almost
the same thing as the base class).
No auto-test, as it's a drag-and-drop related task.
Reviewed-by: Thierry
Task-number: QTBUG-3730
|
|
|
|
| |
Reviewed-by: trust-me
|
|
|
|
|
|
|
|
| |
Auto-test updated.
As a bonus, stabilized tst_QListView::task262152_setModelColumnNavigate.
Reviewed-by: Thierry
|
| |
|
|
|
|
|
|
| |
We now check that the item has children before animating.
Reviewed-by: Alexis
|
|
|
|
|
|
|
|
|
|
|
| |
The flow positions in ScrollPerItem mode did not take the hidden rows into
account when configuring the vertical scroll bar.
A mapping between the scroll bar value and the flow position has been
added. Auto-test included.
Task-number: QTBUG-2233
Reviewed-by: Thierry
|
|\ |
|
| |
| |
| |
| |
| | |
Reviewed-by: thierry
Reviewed-by: pierre
|
| |
| |
| |
| |
| |
| | |
Auto-test included. Will timeout on fail.
Reviewed-by: Alexis
|
| |
| |
| |
| |
| |
| |
| | |
The updated rectangle coordinates didn't use the viewport offsets.
Reviewed-by: Olivier
Task-number: QTBUG-4819
|
|\ \
| |/
|/|
| |
| |
| |
| |
| | |
Conflicts:
src/gui/kernel/qcocoaview_mac.mm
src/network/access/qhttpnetworkconnection.cpp
src/opengl/qgl_qws.cpp
src/opengl/qglpixelbuffer_egl.cpp
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
geometry() is in parent coordinate. We want the coordinate in viewport
coordinate.
There is an offset (the header geometry) between the two.
So the first item was not refreshed.
(Regression because of e5b32fbe0efc8 and a54c18e27bbb)
Reviewed-by: Gabriel
Reviewed-by: Alexis
Task-number: QTBUG-4849
|
| |
| |
| |
| |
| |
| |
| | |
It failed after this commit:
19030e2af098e319e3c3f3883c51e28364bf3ccf
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When the DisplayRole is identical for two or more items, any
modification of one item (e.g. backgroundColorRole) may trigger a
re-ordering, which is obviously not an behaviour to be expected.
Same fix as the one used for QTreewidget in
c9eacfa1c791e2d228a3c8f0c119d02d7f46ee02.
Task-number: QTBUG-4856
Task-number: 262056
Reviewed-by: Olivier Goffart
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Keep the sorting states in sync with the header when
setting custom headers
Reviewed-by: Gabriel
Task-number: QTBUG-3128
task-number: 234926
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When making a rubber band selection while Control is pressed in an
itemview with extended selection, make sure that the selection state
of the items inside the rubber band is toggled.
This ammend commit 0644e3dce532b1df00a77d3a30c61d6b75d3ff30
Merge-request: 1759
Reviewed-by: Olivier Goffart <ogoffart@trolltech.com>
Reviewed-by: Gabriel
Task-number: QTBUG-1435
Task-number: 191545
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | | |
The resolution of conflicts introduced regressions. And the commit
was already in 4.6
|
| | |
| | |
| | |
| | | |
Reviewed-by: trustme
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Keyboard navigation didn't work in the following cases:
- The last column was disabled and we pressed the tab key when at the 2nd
last column. (See ref. task).
- Spans with their anchor column or row hidden or disabled.
- Navigation would not preserve the original row/column when traversing a
span horizontally/vertically.
Auto-tests submitted with this commit.
Task-number: QTBUG-3878
Reviewed-by: Olivier
|