| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The problem was that the 'exposed rectangle' passed to the Item's paint() function was rounded to Int values, whereas the one passed to drawBackground and drawForeground was not.
Autotest included.
Task-number: QTBUG-5859
Reviewed-by: bnilsen
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
make a real fix for the problem is defaulting to sizehint when
there is no preferred size set (ie the toolbar hasn't been moved)
This reverts commit a2c247ed521d88f99a21b4207cdff8ea03e949be.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: Olivier
Task-number: QTBUG-6004
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
All the examples/demos that used a QGraphicsView with a QGLWidget
as a viewport, that had multisampling enabled, was broken after
7b61fbf03e170a7da37d5f57ed4053aae719ec7f. This is because the reparented
QGLWidget will be forced to use the parent widget's visual, which in this
case does not contain any multisample buffers. The QX11Info structure
for QGLWidget is put together based on the QGLFormat that is passed
into the QGLWidget constructor and will in most cases always be
different from the parent widget visual.
Task-number: QTBUG-5998 and QTBUG-6003
Reviewed-by: Eskil
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Task-number: QTBUG-5804
Reviewed-by: denis
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Setting a stylesheet or reparenting a widget into a
widget using style sheet would cause the usesScrollButtons
to be reset. Instead we now keep the flag whenever
it has been explicitly set by the user rather than
querying from the style again.
Task-number: QTBUG-3370
Reviewed-by: jbache
|
| |\ \ \
| | |_|/
| |/| |
| | | | |
into 4.6
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The action performed by the latest drag and drop operation is stored in
the global DnDParams structure. The QDrag::exec() return value has to be
fetcted from this global variable instead of the temporary copy on stack.
Commit 0d231c32cc7670d356d486b13648cb5bd471ffef broke this.
Task-number: QTBUG-6001
Reviewed-by: Denis
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
crashes
Merge-request: 2080
Reviewed-by: Denis Dzyubenko <denis.dzyubenko@nokia.com>
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
On Windows CE the native menubar must not be used.
The corresponding flag was never set for Windows CE.
Task-number: QT-2530
Reviewed-by: Maurice
|
|\ \ \
| |/ /
|/| /
| |/ |
|
| |\
| | |
| | |
| | | |
4.6-staging2
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add logic to make keypad navigation faster when auto repeating.
Task-number: QTBUG-5988
Reviewed-by: Gareth Stockwell
|
| | |
| | |
| | |
| | |
| | | |
Task-number: QTBUG-6011
Reviewed-by: Gareth Stockwell
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Missing virtual function now implemented
Task-number: QTBUG-5977
Reviewed-by: axis
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: ogoffart
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: leo
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Commit ecc202c introduced the regression while fixing another
regression (QTBUG-5854)
The selection would not expend to the whole viewport.
Reviewed-by: Robert Griebl
|
| | |
| | |
| | |
| | |
| | | |
Task-number: QTBUG-4334
Reviewed-by: ogoffart
|
| | |
| | |
| | |
| | |
| | | |
Task-number: QTBUG-1976
Reviewed-by: Gabi
|
| |\ \ |
|
| | |/
| |/|
| | |
| | | |
Task-number: QTBUG-5968
|
| |\ \
| | | |
| | | |
| | | | |
4.6-staging2
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The linker warning that indicates symbol visibility changes is not useful
as it is an expected change to symbol visibility and produces lots of
clutter in the build logs.
(It is not desirable to follow the ELF spec when it comes to symbol
visibility in this case, which is why the linker warns and we ignore it)
This is likely to be a Raptor-only issue - I believe abld suppresses the
warning by default (at least in ABIv1 mode)
Also update gui.pro to use LFLAGS rather than MMP_RULES to alter the
arguments to ARMCC toolchain. qmake ought to detect this (incorrect)
usage of MMP_RULES and abort MMP file generation - raised QTBU-5961 to
look at this.
Reviewed-by: Shane Kearns
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
You have to link to Glib if you're using it...
Reviewed-by: Peter Hartmann
|
| |\ \ \ \ |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When filling in touch point data for delivering to widget don't use the setter
methods to avoid unnecessary detaches. Making it not detach also allows not to
re-calculate widget-relative start position and last position on each delivery
step.
Also use the QWeakPointer to store a pointer to a widget that expects to
receive a touch event, so that if the widget is destroyed we'll get notified.
Reviewed-by: Bradley T. Hughes
|
| |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Conflicts:
configure.exe
|
| |_|_|_|_|/
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Some style relies on this broken behaviour that was fixed in commit
e1a81c96790bee72ee4fbd2b0c4a7b48078c4ec1
The text on the combobox uses the wrong palette role.
Reviewed-by: jbache
|
|\ \ \ \ \ \
| | |_|_|/ /
| |/| | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Over src/ tools/ examples/ and demos/
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Task-number: QTBUG-2494
Reviewed-by: Gabriel
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The previous implementation was scrolling down (number of visible items
in viewport) + 1 and this was leading to one item being skipped while doing
page down (the same also happened for page up). Now we are scrolling (number
of visible items in viewport) - 1 for each page down(up) (the '-1' is for
keeping the context, so the last item will turn into the first in case of
a page down, for example).
Task-number: QTBUG-5877
Reviewed-by: thierry
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The autotest are included
Task-number: QTBUG-5884
Reviewed-by: ogoffart
|
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The execution flow would allow the widget the scene would be rendered on to be
null. However this very widget was being used when using DeviceCoordinateCache
to get the desktop size. We now skip this optimisation when no widget is
given. Auto-test included.
Reviewed-by: bnilsen
Task-number: QTBUG-5904
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
4.6-staging2
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
To get a mobile friendly 1-column layout, we can set
QFormLayout's rowWrapPolicy. S60Style should return
QFormLayout::WrapLongRows as the SH_FormLayoutWrapPolicy
styleHint.
Reviewed-by: Jason Barron
|
| |\ \ \ \ \ |
|
| |\ \ \ \ \ \ |
|
| | | | | | | | |
|
| | | |/ / / /
| | |/| | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The mouse wheel event was not being relayed to the parent (supposedly QAbstractScrollArea) widget. Auto-test included.
Reviewed-by: Olivier
Task-number: QTBUG-5237
|
| | |\ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | | |
4.6-staging2
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
If the webpage does define BODY colors for background, it is possible
that lineEdits are not drawn at all. Actually, they are drawn but with
transparent background, which makes them near-invisible. This is due
to that QS60Style tries to check if the themePalette has been changed
and if it has forwards the drawing of that particular widget to common
style. Common style unfortunately uses active style's palette to draw
the widget. S60Style defines Base to be transparent (to get the
theme background shine through) and common style tries to use Base
to draw lineEdit. End result is transparent lineEdit on webpage.
This fix makes more educated deduction when it tries to see if style
has been changed. This is related to QTBUG-4885.
Task-number: QTBUG-4885
Reviewed-by: Janne Koskinen
|