| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
If you specify an operation that is not recognized in
QT_DIRECTFB_WARN_ON_RASTERFALLBACKS or
QT_DIRECTFB_DISABLE_RASTERFALLBACKS
Reviewed-by: muthu <qt-info@nokia.com>
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
Compile fix for Windows Mobile and OpenGLES2
Wrong dirty region after row selection in right-to-left mode in QTableView
Fixes: Mysql truncation of integer values + some autotest cleanup
|
| |
| |
| |
| | |
The native device is now the default screen device.
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
Wrong dirty region after row selection in right-to-left mode in QTableView
Fixes: Mysql truncation of integer values + some autotest cleanup
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When computing the region from the selection range, we didn't take
care of the actual position of the cells, which is reverted when in
RtoL mode. Also gets fixed a 2-pixel error introduced in commit
718905c097a7f3bbf9805a2561cd855a0b2d8f59, and that was responsible for
(potentialy) painting more cells than needed.
Auto-test included.
Reviewed-by: Olivier
Task-number: QTBUG-7774
|
| | |
| | |
| | |
| | | |
Task-number: QTBUG-5765
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Parent window accepted pointer events even though the child was modal.
That was because closing popup didn't restore pointer grab for modal
window.
Task-number: QTBUG-6659
Reviewed-by: axis
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
QRasterGraphicsSystem tries to create QRasterPixmapData and
QRasterWindowSurface if QApplication::setGraphicsSystem("raster")
is used. On Symbian it should create QS60PixmapData and QS60WindowSurface.
Task-number: QTBUG-8762
Reviewed-by: Jason Barron
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
QProcessManagerMediator and QProcessActive were not properly canceled
in their destructors, causing crash when global static QProcessManager
was deleted.
Task-number: QTBUG-7735
Reviewed-by: Janne Anttila
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Currently: QS60Style does not polish widgets with highlight colors.
Instead it fetches color information from native theme side and uses
that color for drawing the text.
http://bugreports.qt.nokia.com/browse/QTBUG-8704
Fix: All widgets with highlighted text (lists, tables, headers, tabs,
radiobuttons and checkboxes) polish their palette. This palette
value is then used in the drawing code. Earlier it was not possible
for developers to define their own highlight text color, now it is
possible.
Task-number: QTBUG-8704
Reviewed-by: Janne Anttila
|
|\ \ \ |
|
| |/ /
| | |
| | |
| | | |
Reviewed-By: TrustMe
|
| |\ \
| | |/
| |/|
| | |
| | |
| | |
| | | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/qt-s60-public:
Fixed crash in Symbian when having empty QMenu in menubar.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Typically cascade menus in Symbian/S60 are created from resources.
When cascade menus are defined in resources the RestoreMenuL is
responsible for instantiating the cascade menu item array and items.
In Qt for Symbian the menus need to be created dynamically from
QActions, that's why RestoreMenuL is reimplemeted in Qt for Symbian
to dynamically init the menu pane content. Adding a first dynamic
item to cascase menu pane creates the CEikMenuPane internal item array.
In case where empty QMenu was added to QMenubar, the item array for
cascade menupane was never constructed. Then later on CEikMenuPane code
assumes that item array exist. To avoid access violation crash we now
create the item array manually when building submenu.
Task-number: QTBUG-4897
Reviewed-by: Jason Barron
|
| | |
| | |
| | |
| | | |
Task-number: QTBUG-8752
|
| |\ \ |
|
| | |\ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
When using OpenVG alpha mask, turn off scissor-as-mask
|
| | |\ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/qt-multimedia-staging:
Linux QAudioOutput playback stuttering
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Adjust buffer and period sizes if system cannot work with defaults
(alsa).
Task-number:QTBUG-8339
Reviewed-by:Derick Hawcroft
|
| | |\ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-1:
tst_qhostinfo: Compile fix
Document some stuff in QHostInfo and QAbstractSocket
tst_qhostinfo: Mixed up descriptions for test case data
qhostinfo benchmark: Use local _data instead of _global
DNS Cache: Also check inside the DNS threads
qhostinfo benchmark: Benchmark the with-cache and without-cache
tst_qftp: Do not use 1.2.3.4 as IP
Dont use gestures if there is no touch screen.
showFullscreen() broken if UnifiedTitleAndToolBarOnMac is enabled
Fix atk warning on startup in Qt apps wit QGtkStyle
Do not use realpath() with uclibc
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Reviewed-by: joao
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
If there is no touch input device attached on Windows7, we shouldn't even
bother subscribing to native gesture events.
Task-number: QTBUG-6007
Reviewed-by: Thierry
Reviewed-by: Prasanth
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The problem here is caused by the fix to QTBUG-6200. For this fix we
removed the lines that deleted the item because the iterator might be
invalid at that point. However, we still need to delete the iterator. The
solution is to not use the iterator and ask the hash to delete the item,
since the remove function will not crash if the item is invalid.
Task-number: QTBUG-8633
Reviewed-by: Prasanth
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
While this is acknowledged as a bug in Gtk+ and confirmed
fixed upstream, since some distros such as Ubuntu are not
backporting this fix and it is easy to work around we should
simply fix this for 4.6.3 instead. The problem is simply that
atk assumes the button has a label or a labeled icon and
spits out a warning if it does not.
Additional info can be found here:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/484182
Reviewed-by:thorbjorn
Task-number: QTBUG-8425
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Task-number: QTBUG-8365
Reviewed-by: denis
|
| | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Path transforms need to be adjusted by 0.5 for the difference
in OpenVG and Qt co-ordinate systems. Image transforms do not
need to be adjusted because OpenVG implicitly adjusts by 0.5.
Task-number: QT-2999
Reviewed-by: Sarah Smith
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | | |
Task-number: QT-3033
Reviewed-by: Julian de Bhal
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
QWS will make a window translucent if the background brush is not
opaque. Now we also support the cross-platform way of doing it.
This also includes fixes for bugs caused by behavioural changes in
the internal windowsurface/backingstore implementation.
Task-number: QTBUG-5739
Reviewed-by: Tom
|
| |\ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
Make tablet detection work with new wacom drivers
Fixed an exit crash that could occur in the GL 2 engine under X11.
Fix tst_QVariant::operator_eq_eq(UserType)
SqlBrowser not respecting casings.
Remove vgClearPath() change to OpenVG paint engine
QVariant: Fix crash when comparing two variant with the same undefined type.
Fix compositing when QWS background is completely transparent.
Fixes wrong composition mode for cached backgrounds in Graphics View.
Support keypad input with vnc driver
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
wacom driver fixed a bug in assigning atom names where it messed
up the device names. Their solution apparently renamed the atoms
The type names used now are "STYLUS", "CURSOR", "ERASER", "PAD"
and "TOUCH" for each respective device. This change detects
those as our tablet input devices.
Reviewed-by: Benjamin Poulain <benjamin.poulain@nokia.com>
Task-number: QTBUG-8599
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The global destructor for the clean up hooks might be called before the
global destructor for QPixmap objects. We shouldn't leave pixmaps
around that is destroyed after the QApplication destructor is called.
Task-number: QTBUG-8681
Reviewed-by: Tom Cooksey
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It was comparing uninitialized memory.
Reviewed-by: Thierry
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Upon further investigation, vgClearPath() doesn't help as much
on target devices as just making a new path.
Revert "Improve performance of VGPath creation by reusing the same path"
This reverts commit 8597e03495f54614e53c6063f1f13077a08109fd.
|
| | |\ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
QVariant: Fix crash when comparing two variant with the same undefined type.
Fix compositing when QWS background is completely transparent.
Fixes wrong composition mode for cached backgrounds in Graphics View.
Support keypad input with vnc driver
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
If the type is the same, but not registered, the returned string could be
null (or empty if a empty string was registered)
In that case, QVariant compare() function would access invalid memory.
Protect against that case. qstrcmp returns 0 if 0 is given as a parametter.
Task-number: QTBUG-8700
Reviewed-by: Markus Goetz
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Specifying the wrong composition mode triggered an optimization which
caused uninitialized values to be blended in.
Task-number: QTBUG-6625, QTBUG-6906
Reviewed-by: Samuel
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This change partially reverts commit a589005f and therefore fully reverts
68be6457. We cannot assume that only opaque pixels are painted in
drawBackground().
Regression against 4.5. Auto-test included.
Task-number: QTBUG-8168
Reviewed-by: trond
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Task-number: QT-1849
Reviewed-by: Jeremy
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
We do not officially support static loading of icons.
In fact they still crash for simple png cases due to missing
X11 resources. But since we lazily create themed icons
we can certainly avoid the crash in this case. You will
not be able to use fallbacks here though, since we cannot
know if a fallback should be used or not in this case.
Reviewed-by: ogoffart
Task-number: QTBUG-8666
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Task-number: QTBUG-8729
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Calling QString::utf16() will cause reallocation (for null-termination)
if the string was created via fromRawData().
Reviewed-by: Benjamin Poulain
Reviewed-by: Simon Hausmann
|
| |\ \ \ \
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-1:
Removed unused macro.
Fix runtime warning on Gtk versions < 2.16
Fix compile
Follow-up to c1b067e: fix aliasing in QReadWriteLock too.
Bug with toolbar focus on Mac
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reviewed-by: Stefano Pironato
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The label property was not added until version 2.16 of
Gtk+ and using it will trigger a warning on older versions.
Instead we create it with the label set instead which should
work for 2.0 and up.
Task-number: QTBUG-8537
Reviewed-by: Harald Fernengel
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reviewed-by: cduclos
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The same pattern used in QMutexLocker was used in QReadLocker and
QWriteLocker.
Reviewed-by: Trust Me
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Before doing anything we need to make sure that we don't leave anything
in a non-consistent state. When hiding a widget we need to make sure that
no mouse_down events are active, because the mouse_up event will never be
received by a hidden widget or one of its descendants. The solution is
simple, before going through with this we check if there are any
mouse_down events in progress, if so we check if it is related to this
widget or not. If so, we just reset the mouse_down and then we continue.
In X11 and Windows we send a mouse_release event, however we don't do that
here because we were already ignoring that from before. I.e. Carbon did
not send the mouse release event, so we will not send the mouse release
event. There are two ways to interpret this:
1. If we don't send the mouse release event, the widget might get into an
inconsistent state, i.e. it might be waiting for a release event that
will never arrive.
2. If we send the mouse release event, then the widget might decide to
trigger an action that is not supposed to trigger because it is not visible.
Task-number: QTBUG-8604
Reviewed-by: denis
|
| |\ \ \ \
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
Properly fixes crash when destroying a QGraphicsItem.
Updating SQL binding docs to reflect reality.
|