| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the menu bar is subject to height for width (HFW) we should of
course respect that, but in addition we should ensure that the HFW is
within the minimum and maximum height. This also is consistent with how
QGridLayout calculates the effective minimum row height.
This fixes a regression because change 4780f94e391b5e881497c5228661dead
turned QTabWidget into a proper height-for-width citizen, and when
setting a QTabWidget as a menuwidget, the buggy codepath for HFW was
suddenly hit in menuBarHeightForWidth().
Task-number: QTBUG-31057
Reviewed-by: Paul Olav Tvete <paul.tvete@digia.com>
(cherry picked from qtbase/27e690e163408dec1e9c56ffc07131354d4b2c8a)
Change-Id: I915d37c69152c1804925000303e82a3fae5a9a47
Reviewed-by: Paul Olav Tvete <paul.tvete@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Similar to what change a298216bb4383dbe96 does for update(QRect) we clip
the update region against the widget's rect and return if it's empty.
Otherwise we risk ending up with update rects that are larger than
INT_MAX due to multiple update rects being merged.
Task-number: QTBUG-30876
Change-Id: Idf695b1fdca50449a1e5ddf37500653de290590c
Reviewed-by: Gunnar Sletta <gunnar.sletta@digia.com>
(cherry picked from commit 69ee30260a667b2b977a0d4b52abf6537521cce8)
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can simply clip the update rect against the widget's rect and return
if it's empty. Otherwise we risk ending up with update rects that are
larger than INT_MAX due to multiple update rects being merged.
Task-number: QTBUG-30876
Change-Id: I23bd0149fbe8d1a007a60b228e6bddb45dc4fc32
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Reviewed-by: Gunnar Sletta <gunnar.sletta@digia.com>
(cherry picked from commit a298216bb4383dbe96688dfb80da0cd875766de0)
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously if l had a parent, addChildLayout would warn and skip the
reparenting, but it would still add the sub layout to the layout.
This caused some inconsistencies in the hierarchy which in worst case
could cause crashes.
Task-number: QTBUG-30758
(cherry-picked from qtbase commit 146658a10f290603470b800d71b778239e764312)
Change-Id: Iee6ace3189620395d7670007a23783823ed616b9
Reviewed-by: Paul Olav Tvete <paul.tvete@digia.com>
|
|
|
|
|
|
|
|
| |
becomeDelegteForWindow -> becomeDelegateForWindow
Task-number: QTBUG-30754
Change-Id: Ied7fba42c642deb2c22ff414069659a62cb1a200
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
|
|
|
|
|
|
|
|
|
|
| |
Clang doesn't like the extra qualification in the forward declaration. Let's
move the forward declaration outside of the Qt namespace, which is better anyway
since TabletProximityRec is defined in the Apple headers/global namespace.
Task-number: QTBUG-29373
Change-Id: Iba59e6592ccbbcc09e91e1b9831a0ee588469b23
Reviewed-by: Morten Johan Sørvig <morten.sorvig@digia.com>
|
|
|
|
|
|
|
| |
userSpaceScaleFactor is deprecated.
Change-Id: I892cb579e4b3ef9226495759c884d0e74c85a1d6
Reviewed-by: Gabriel de Dietrich <gabriel.dedietrich@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
Not currently considering activation state.
backport from qt5 8dc2f81c9f0e6eb8cab09e5d682358fd140b49b8
Change-Id: Ib46e554b08cc8d15f83e9865a8f0be3f8d7b9d16
Reviewed-by: Samuel Rødal <samuel.rodal@digia.com>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
|
|
|
|
|
|
|
|
|
|
|
| |
We also have to make sure that when moving back to a page
that has a focusWidget(), the focus should go to the focusWidget()
Task-number: QTBUG-18242
Change-Id: Ibfa7d6361c1a456480b2f1584a88ef4c4f405709
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
(cherry picked from qtbase/18f9eb797bffe8626f1edeca3c88f80dae0da8d7)
|
|
|
|
|
|
|
|
|
|
|
|
| |
If QApplication has not been instantiated, this function would
crash. Change it to return NULL pointer instead.
cherry-picked from qt5/qtbase 3ee48926e6584b4afeda1fc406d19d7b1a8d6f20
original patch from Miikka Heikkinen <miikka.heikkinen@digia.com>
Change-Id: Ic9aae241f9c424fb371ae1774da6a3cb28c31883
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@digia.com>
Reviewed-by: Jørgen Lind <jorgen.lind@gmail.com>
|
|
|
|
|
| |
Change-Id: I5d62fcf0880776e290ae739ece81b685bb7af194
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>
|
|
|
|
|
|
|
|
|
| |
When show/hide is called on a widget on Mac then it needs to send an
enter/leave event. But it should only do that if the widget under the
mouse is actually the one that is being shown/hidden.
Change-Id: I53c782f5deee740cbc34e1fcc7b551a108230081
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Fix MinGW compile breakage introduced by
68331c5436506b6f9b4c2a49692a09020e4eef27 .
Task-number: QTBUG-8764
Task-number: QTBUG-10032
Change-Id: I26bcefc382010eee7d79b806b3d9f08b6cb2ff8d
Reviewed-by: Rafael Roquetto <rafael.roquetto@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Depending on the implementation updating an input method can be
expensive and various widgets will at times call setInputMethodHints
with unchanged hints. QGraphicsView being a notable offender due to
the complexity of the circumstances in which the hints can change.
Skipping the update here ensures the input method isn't updated
unnecessarily for all widgets.
Task-number: QTBUG-19854
Reviewed-by: Gunnar Sletta <gunnar.sletta@digia.com>
(cherry picked from commit 40e6b1d0b8c1804dfb33032fa70b6604b91f6f90)
Change-Id: I36ae35585ee20a4e01ca0d62c71e896dbdb51a3f
Reviewed-by: Gunnar Sletta <gunnar.sletta@digia.com>
|
|
|
|
|
|
|
|
| |
Nothing is used from the above header files so these dead includes can
be removed.
Change-Id: I381ea62e5a0bc623bb984c764be55c7a2f2ee317
Reviewed-by: Samuel Rødal <samuel.rodal@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
Fix compilation issue when QT_NO_IM is defined.
Also fixed references in tests. But fixing
plugins/examples seem not necessary at this point.
Task-number: QTBUG-26109
Change-Id: I2067051951616012117efa6716640cbf198fdb2a
Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@digia.com>
|
|
|
|
|
|
|
| |
Change-Id: Iadb89137ec017b9dcd4d1588fd582ea46a9d7cc1
Reviewed-by: Aurelien <aurelien.lourot@gmail.com>
Reviewed-by: David Faure (KDE) <faure@kde.org>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since Qt4, there is a bug which causes Qt to drop dead key modifiers
(like graves and acutes) if the user types enough fast on MS Windows.
This happens because of an extrange behavior of Windows, which drops
dead keys on ToUnicode() calls.
This patch tries to workaround that.
Task-number: QTBUG-8764
Task-number: QTBUG-10032
Conflicts:
src/plugins/platforms/windows/qwindowskeymapper.cpp
Change-Id: Ifdde25817743194fd5c0b7533c27f46a7a108ca4
(cherry picked from commit 5d2bb24cc90194a3458f8741e30ae7afe0b45f5c)
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
If a tool window is ordered out when there is a full screen widget
around then it would cause a crash because of a new animation from
Lion. This seems to be provoked by the fact that we are faking the
fullscreen functionality in Qt.
Change-Id: I07cdfddc6c2bb766df7809912fb97c4f1ba8873b
Reviewed-by: Morten Johan Sørvig <morten.sorvig@digia.com>
|
|
|
|
|
|
| |
Change-Id: I52bf8ef0447b701b4ebf7d7d240013a72adb9425
Reviewed-by: Akseli Salovaara <akseli.salovaara@digia.com>
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When showing full screen, we need to enforce that the size of the widget *is*
the size of the screen. When calling QWidget::resize(), there was a chance for
the layout to bypass the screen size, causing the toplevel widget to be
clipped.
This fix is not necessary on Qt5. Qt5 implements this differently and
correctly.
Change-Id: I1f4467dd14310ee20376caba8780507f8d787720
Reviewed-by: Samuel Rødal <samuel.rodal@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We must check within QWidgetPrivate::hide_sys() if the widget has a platform
window and hide it.
Fixed on Qt5 as a side effect of 09163941268745bbe231d0b2c25697940aa40127
Change-Id: Id0f5e748e69789027cbde427d37655d19a4ccab2
Reviewed-by: Sean Harmer <sean.harmer@kdab.com>
Reviewed-by: Kevin Krammer <kevin.krammer@kdab.com>
Reviewed-by: Debao Zhang <hello@debao.me>
Reviewed-by: Jørgen Lind <jorgen.lind@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
Based on qt5 4469de4ce7a72ab6824629bfe8483131aaf22137
Change-Id: I5886c11f3dcf72943e2956beaa92464657110ce9
Reviewed-by: Laszlo Agocs <lagocs83@gmail.com>
Reviewed-by: Sérgio Martins <sergio.martins.qnx@kdab.com>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: Sean Harmer <sean.harmer@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The BPS version provided by the current version of the Playbook OS does not
support orientation locking. This patch implements this manually.
This patch is not needed in Qt5, since the API has changed.
Change-Id: Ibba6fb3437cb392e3ba3d2b1997a178653226131
Reviewed-by: Nicolas Arnaud-Cormos <nicolas@kdab.com>
Reviewed-by: Bernd Weimer <bweimer@rim.com>
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QStackedLayout doesn't have support for QLayout, only QWidget, so
the issue doesn't arise there.
(cherry-picked from qtbase/716d33d2a73ade42eb31be3e8ecbaeecdd5ddd21)
(only change: s/reset()/clear()/ in the tests)
Reported-by: Johannes Schaub
Task-number: QTBUG-27420
Change-Id: I7f3c4b1996e954428c00d4dda1095712efa91367
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
|
|
|
|
|
|
|
|
|
| |
Since graphics effects on widgets are not supported on Mac then the
code is #ifdef'd out so that it does not crash instead.
Task-number: QTBUG-24792
Change-Id: I4d81675b54816fa60cf66696b1a0a7b0206474e3
Reviewed-by: Morten Johan Sørvig <morten.sorvig@digia.com>
|
|
|
|
|
|
|
|
|
| |
Fix for QTBUG-27607. Now it handles the setMaxWindowRect for fullscreen
widgets. It is called when the resolution changes with QWS.
Change-Id: I0fdbb39c55f727b6507fbb14369943dd8b7c2d7e
Reviewed-by: Samuli Piippo <samuli.piippo@digia.com>
Reviewed-by: Paul Olav Tvete <paul.tvete@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On X11 if you have multiple tablet input devices, like a Wacom Cintiq and
a Wacom Intuos tablet connected at the same time, one of the tablets will
generate incorrect high resolution coordinates.
The reason seems to be that when translating the XEvent in
qapplication_X11.cpp the code searches for the first tablet device it
finds that supports the type of the current event. Since both tablets
will support this event type, we wind up always finding only one of the
tablets. Specifically, the first tablet that was found when enumerating
tablets during qt_init. Then all calls to QTabletDeviceData::scaleCoord
are made on the same device, so the size of one of the devices is never
used. That device will wind up with incorrect high resolution
coordinates.
When not running under IRIX the XEvent will have a deviceid which we can
use to find the correct device to use for scaling. This change
implements that fix.
Change-Id: I667a52a729273a9b12880592d0a4cd7ce7f16106
Reviewed-by: Gunnar Sletta <gunnar.sletta@digia.com>
Reviewed-by: Konstantin Ritt <ritt.ks@gmail.com>
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Only one event type can be passed to the event filter in Qt4. For the
BlackBerry platform this will be BPS events. This should be acceptable,
as there isn't any documentation stating that it should be window system
events for QPA ports.
In Qt5 the implementation is different (it is possible to pass the event
type along with the event itself).
Change-Id: I95550cec8a04a4994479904bc68544742a458aa9
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QKeyEvent::key() returned the wrong value if the ctrl modifier was used
in that key event. That was due to the fact that ToUnicode might not
return the correct code for these events/keyboard states. While it works
for alt+shift+= (us layout) and gives '+' as unicode value it just
claims that it cannot translate the given state for ctrl+shift+=. So if
the control modifier is used and ToUnicode return 0 toKeyOrUnicode
should try again without the control modifier.
Task-number: QTBUG-10781
Change-Id: I771f7ed18bcce60d1c7c3f6157d169d4e80ddd60
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@digia.com>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
Newer Linuxes have a symlink named 'exe' to the executable
and 'cmdline' is empty.
Task-number: QTBUG-27632
Change-Id: I45eb2186e2608e9600c4b6b27a033d8b1350deee
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously recommended fonts sizes in pixels do not work very well
on the new high resolution devices.
Current UX documentation recommends point size 8 for normal text
which works well on both types of devices.
Backport of qtbase 4d693b6cdf879a03f77f2a06ca0e1be5605c0fc0
Change-Id: I9507b77a5e814b33cf90e714ae62d64e468710b9
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
Reviewed-by: Sean Harmer <sean.harmer@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Qt::WA_LockPortraitOrientation and Qt::WA_LockLandscapeOrientation
will be adhered to.
This is not needed in Qt5, as those attributes have been removed from Qt5.
Change-Id: I5f29cad0e2c784caa6201b683d7b658a5b0d083d
Reviewed-by: Fabian Bumberger <fbumberger@rim.com>
Reviewed-by: Kevin Krammer <kevin.krammer@kdab.com>
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed QComboBox popup issue which was left open if window
was moved(dragged) to another position.
Task-number: QTBUG-1894
Task-number: QTBUG-26120
Task-number: QTBUG-26465
Task-number: QTBUG-26827
Change-Id: I7e37b37881cdf94574d79f7e77d36f5bbc15f732
Reviewed-by: Andy Shaw <andy.shaw@digia.com>
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Task-number: QTBUG-27265
Don't check "dragOverWidget != widget" in QOleDropTarget::DragOver()
because if the dropsite widget's parent widget is the drop target this
check will prevent its parent widget receive drag over event and the dnd
cursor indicator is also wrong.
We replace the check with "!dragOverWidget->isWindow()" to prevent pass
through a window.
A similar issue in Qt5 beta has been fixed by
https://codereview.qt-project.org/#change,35646
Change-Id: I9e18b71bd7f3ee244db61571811c51dc16b341d2
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
Reviewed-by: Marc Mutz <marc.mutz@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Ensure Qt's native implementation of sendEvent: calls the proper Qt
event filters and passes them along to the correct QApplication
instance thus guaranteeing that macEventFilter() is properly called
when a non namespaced and a namespaced Qt exists in one process.
Change-Id: I61543d6ef68b09cfb40c9d263aaaf5ead5ece24b
Reviewed-by: Yan Shapochnik <shapochniky@seapine.com>
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ensure the correct QNSApplication is referenced when multiple Qt
instances exist in a process. This will also prevent the following
messages from being displayed in the console "Class QNSApplication
is implemented in both /path/to/QtGui.framework/Versions/4/QtGui and
/path/QtGuiNamespaced.framework/Versions/4/QtGuiNamespaced. One of the
two will be used. Which one is undefined.
Change-Id: I22e7f06aa35e9daecf2e9c881268baf92d35022c
Reviewed-by: Janne Anttila <janne.anttila@digia.com>
Reviewed-by: Teemu Katajisto <teemu.katajisto@digia.com>
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This event can be used by any platform plugin to implement
special application panels/overlayed menus.
Currently used by QNX only.
This replaces sending fake Qt::Key_Menu presses in the QNX
plugin. Qt::Key_Menu is already used when invoking context
menus with the keyboard.
( backport of qtbase/9695df4d44b228e7e778ff17d5cccac30967b1fd )
Change-Id: Id5cf96758f1104f454a2bb977b367d09d4685b62
Reviewed-by: Paul Olav Tvete <paul.tvete@digia.com>
Reviewed-by: Kevin Krammer <kevin.krammer@kdab.com>
|
|
|
|
|
|
|
|
|
|
| |
- Assigned/Unused variables.
- Unsigned comparison >= 0 is always true.
- Constructor initialization order.
- Signed/Unsigned comparisons.
Change-Id: I1f9edab0506573420ed0bf3055252ba48625c8eb
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
|
|
|
|
|
|
|
|
| |
Change copyrights and license headers from Nokia to Digia
Change-Id: I280c0a575987d1770e354b4948f1d4d767d711ea
Reviewed-by: Simo Fält <simo.falt@digia.com>
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Always clear the XSizeHints before retrieving with XGetWMNormalHints
because if the window doesn't have size hints set the structure will
remain uninitalized. Clear XSizeHints in other locations as well just
to be safe.
Task-number: QTBUG-15418
Change-Id: Ia9a0c485389bf27016ee7f206a3a916d0bbcbcfa
Signed-off-by: David Fries <David@Fries.net>
Reviewed-by: Marc Mutz <marc.mutz@kdab.com>
|
|
|
|
|
|
|
|
|
| |
When Qt was built statically then the Mac specific resources were not
being loaded which meant some style specific images were not used.
Task-number: QTBUG-25391
Change-Id: Iad538b5f1935ed1744617d6e47ae3e68aa36afac
Reviewed-by: Morten Johan Sørvig <morten.sorvig@digia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Task-number: QTBUG-27263
QWExtra object pointer is not guaranteed to be valid in
QWidget::unregisterOldDnd() since commit
f6bf4b2baa91e55f40596bf3f2823b119fdfa5e0. To avoid crash we have to check
QWExtra object pointer of the native parent widget before access it, and
if the pointer is not valid we should check its native parent widget
recursively.
Change-Id: I764fea4a0826cff751dd74a0fb67e0d2971c1d49
Reviewed-by: Miikka Heikkinen <miikka.heikkinen@digia.com>
Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
NSEvent for mouse events contain the mouse position in floating
point numbers. This value is truncated/floored for mouse clicks.
Qt instead rounds that value, so mouse move events can get positions
that are slightly off sometimes. This solves #QTBUG-27273.
Change-Id: I2d3f59a09f50cb83dc1ccf6de940b7d99087c9ee
Reviewed-by: Morten Johan Sørvig <morten.sorvig@digia.com>
|
|
|
|
|
|
|
|
|
|
| |
If the sendEvent function is replaced on the NSApplication, then
QApplication should ensure that it undoes that if it is destroyed while
the NSApplication is still running.
Task-number: QTBUG-24248
Change-Id: I087ae575b7d670fa8dacfb80636d813c7bceb41d
Reviewed-by: Richard Moe Gustavsen <richard.gustavsen@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Qt::KeypadModifier modifier is internally masked away from all
shortcuts. So it is not possible to set a keypad only shortcut.
Changed the implementation so that first a full keysequence match is
searched. Then if no match is found the same sequence is tried
without the keypad modifer.
Added a autotest for this also to cover the basic use cases relating
to this.
This is a backport of qt5 commit:
547a1bea492954d828aa0798be93384669812489
Task-number: QTBUG-20191
Change-Id: Ibb6809050ff6da23bdb1c087b93e517d1963d34c
Reviewed-by: Stephen Kelly <stephen.kelly@kdab.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When hitting on a child widget that does not accept drops,
go up the hierarchy until the parent is hit or a widget
that accepts drops is found.
Introduced by f6bf4b2baa91e55f40596bf3f2823b119fdfa5e0 .
Task-number: QTBUG-22987
Task-number: QTBUG-27037
Change-Id: I4d9308942c1109c11f7e31555d4ad84fa2610d15
Reviewed-by: Markku Tapio Heikkilä <markku.heikkila@digia.com>
Reviewed-by: Lars Knoll <lars.knoll@nokia.com>
|
|
|
|
|
|
|
| |
Task-number: QTBUG-26891
Change-Id: I9b726d8766337fbb001afcb9ecbc45f51b6e363f
Reviewed-by: Casper van Donderen <casper.vandonderen@nokia.com>
(cherry picked from commit 75901712f04eceafd164cbbf752c916070b44507)
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These files where skipped when tst_license was enabled a while
ago since they had a different license header that didn't match
our test.
Fix these licenses and stop skipping them in tst_license.cpp
Change-Id: I14b2aa1b7c794894c2c74aedab01ff8667621003
Reviewed-by: Thomas McGuire <thomas.mcguire@kdab.com>
Reviewed-by: Kevin Krammer <kevin.krammer@kdab.com>
Reviewed-by: Sean Harmer <sean.harmer@kdab.com>
|
|
|
|
|
|
|
|
|
| |
delay deco widget freeing because the pointer to it
is still available to the drag operation.
Task-number: QTBUG-19363
Change-Id: I775864f72d7151c9fbd26feff5a9bd844f87f292
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
|