| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Task-number: QTBUG-6810
|
|
|
|
|
|
|
|
|
|
|
|
| |
Happens for example if a DockWidget is undocked and has a child
whith the WA_StaticContents attribute.
The parent does not change (so newParent is false) but still, the
top level widget change. So staticWidget need to be moved to the
new backingstore.
Reviewed-by: Benjamin Poulain
Task-number: QTBUG-6883
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
qt-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
Export QGLShareRegister because qgl_share_reg() is exported
Fix upside down PVR compressed textures.
Make sure a context is current when loading compressed textures.
Fix possible off-by-one inconsistency against system look and feel when
Fixes broken graphics effect auto tests.
Doc: Explicitly mention that QWidget/QGraphicsItem takes ownership of effects.
Remove id property from QGraphicsObject
Minor fixes to softkey dimming support (commit 245c9cc0).
FEP returns the wrong foreground color in GetFormatOfFepInlineText
|
| | |
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
qt-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2:
Fix GL_BGRA formats under OpenGL/ES systems
Compilation fix
Assert in designer while drag & dropping items from a QListWidget
Fixed memory leaks when removing a QGraphicsEffect from a QGraphicsItem or QWidget
Fix the toolbars docking
Added dimming support for disabled softkeys in Symbian.
Remove compilation warning from S60pixelMetrics on ARM
Button and LineEdit/TextEdit theme colors are incorrect
QS60Style: Overwrites correct stylehint color values
MMP_RULES overriding qmake variables now warns user
Switched S60 QDesktopServices implementation to CDocumentHandler based.
Fixed "...QString::QString(const char *)... is deprecated" warning.
Unnecessary symbian version checks in sqldrivers.pro
QS60Style: Always store changed theme palette
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
QWidget
with setGraphicsEffect(0).
The effect was not deleted in that case, problem solved for both QGraphicsItem
and QWidget.
Autotest included.
Task-number: QTBUG-5917
Reviewed-by: bnilsen
|
|\ \
| |/
| |
| |
| |
| | |
Conflicts:
src/gui/kernel/qcocoapanel_mac.mm
src/gui/kernel/qcocoawindow_mac.mm
|
| |
| |
| |
| | |
RevBy: Trust me
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
If the touch event comes from a touchpad it doesn't seem necessary to send fake
mouse events. At least on the platform that actually supports touchpad events
(i.e. Mac) native apps don't do that and the current implementation breaks
popup handling - since touch events are only sent by default if two or more
fingers touch the touchpad, we send fake MouseButtonPress when second finger is
pressed and MouseButtonRelease when the second finger is released - i.e. at the
same time when the system send scrollWheel events. This causes the active popup
to close when using two-finger scroll gesture.
Reviewed-by: Brad
|
|
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
|
| |
Task-number: QTBUG-5804
Reviewed-by: denis
|
|\
| |
| |
| |
| | |
Conflicts:
configure.exe
|
| |
| |
| |
| | |
Task-number: QTBUG-5432
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When enabling/disabling a widget or changing its InputMethodEnabled attribute,
use the focus proxy widget's input context for reset and for setting the focus
widget on the input context.
Task-number: QTBUG-5781
Reviewed-by: Denis
|
|\ \
| |/ |
|
| |
| |
| |
| | |
And not rely on random QT_USE_NAMESPACE being pulled in from *.moc files.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Get rid of QGraphicsEffectSource from the public API, instead add
convenience functions in QGraphicsEffect. This way we commit to less
API, and are free to introduce a customizable QGraphicsEffectSource
in a future release.
* Move PixmapPadMode into QGraphicsEffect and tweak the names of the
enum values.
* Make QGraphicsBlurEffect::BlurHint into a bit flag, for extensibility.
Reviewed-by: Bjørn Erik Nilsen
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
| |
| |
| |
| | |
Reviewed-by: owolff
|
|\ \
| | |
| | |
| | |
| | | |
Conflicts:
src/corelib/tools/qscopedpointer.h
|
| | |
| | |
| | |
| | | |
And not rely on random QT_USE_NAMESPACE being pulled in from *.moc files.
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Get rid of QGraphicsEffectSource from the public API, instead add
convenience functions in QGraphicsEffect. This way we commit to less
API, and are free to introduce a customizable QGraphicsEffectSource
in a future release.
* Move PixmapPadMode into QGraphicsEffect and tweak the names of the
enum values.
* Make QGraphicsBlurEffect::BlurHint into a bit flag, for extensibility.
Reviewed-by: Bjørn Erik Nilsen
|
|/
|
|
| |
Reviewed-by: TrustMe
|
|
|
|
|
|
|
|
|
| |
We need to use isOpaque to check whether the widget has an opaque
background, it's not enough to just check the palette (it doesn't check
Qt::NoSystemBackground for example).
Task-number: QTBUG-5012
Reviewed-by: Gunnar Sletta
|
|
|
|
|
|
|
| |
It depends on QT_NO_GRAPHICSVIEW for now, but it is possible to remove
this dependency.
Reviewed-by: paul
|
|\
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| | |
Oops, apparently we forgot to add a function for unsubscribing a
graphics object from a gesture. Fixing it now.
Reviewed-by: trustme
|
| |\ |
|
|\ \ \ |
|
| |\ \ \
| | | |/
| | |/| |
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: Denis Dzyubenko
|
| |\ \ \
| | |_|/
| |/| |
| | | |
| | | | |
Conflicts:
src/gui/effects/qgraphicseffect.cpp
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The opaque children cache was clipped to all the ancestors up to the
top-level, which means whenever a widget changes geometry all the
children must be invalidated. However, the bug was that we didn't
invalidate the children, and that is of course slow so we don't want
to do it either. A better solution is to only clip the children cache to the
widget itself (widget->rect() instead of widget->clipRect()), and we can
perfectly do this because the region we subtract the opaque children from is
already inside the clipRect().
Auto-test included.
Task-number: QTBUG-4245 (related to)
|
| |/
| |
| |
| |
| |
| | |
Usable for future optimizations.
Reviewed-by: Samuel
|
| |
| |
| |
| | |
Reviewed-by: tom
|
|/
|
|
|
|
| |
However, compiling with QT_NO_ICON will still not work :(
Reviewed-by: tom
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem occurred on Windows due to a call to repaint() on a top-level
window from setDisabledStyle() in qwidget.cpp. This function is called
whenever a window is blocking. In this particular case the children of
the repainted window are opaque, and should therefore not be repainted,
which also means that the top-level have to subtract the region of the
opaque children when filling the background. This region is cached,
and the problem was that the cached region was wrong. It was wrong
because it was not invalidated properly.
Task: QTBUG-4245
Reviewed-by: Paul
|
| |
| |
| |
| | |
Reviewed-by: Trust Me
|
|\ \ |
|
| |\ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The original report was that the customer did resize(main.sizeHint())
instead of the main.adjustSize(); Note that resize(main.sizeHint() still does
not work. However, calling main.adjustSize() should now do what the original
reporter wanted.
The problem was that the resize did not work, because at the point of the resize
the minimumHeight of main was still 22 (8+6+8), and we tried to resize it with
a new height of 10. The resize would bound the height up to 22, and the main
widget would then get a size of (200x22).
The reason why it still had a minimumHeight of 22 was that it was the
minimumSize of the previous layout configuration. Unfortunately the new
minimumSize of the widget hadn't been updated yet because there was a
LayoutRequest event in the queue that hadn't been processed yet. (This
LayoutRequest was triggered by that we called invalidate() from hide()).
Thus, processing the event queue immediately after the hide() could also have
been a workaround for this issue.
There is no really good fix for this issue (and it does not seem to be a
common problem) without introducing a risk for regressions.
Due to that we therefore decided to provide a fix in QWidget::adjustSize().
Reviewed-by: paul
|
| |\ \ \ |
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
QGraphicsView.
The main problem here is that QWidget assume that they are in the screen
somewhere, which means inside the available geometry provided by
QDesktopWidget. But in QGraphicsView the button can be in a position
that is way bigger than the screen resolution. Lot of widgets make
this assumption when positionning subpopups or submenus. Instead of
applying the same code on tons of QWidgets, it's better to have an
helper function in desktop widget which catch this case. It's not
pretty (since it has nothing to do with QDesktopWidget) but we don't
have better solution.
Task-number:QTBUG-3822
Reviewed-by:brad
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
If an effect is applied repeatedly on the same source, just with
varying parameters, we can save a lot by caching the source pixmaps.
Reviewed-by: Bjørn Erik Nilsen
|
|\ \ \ |
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/corelib/kernel/qcoreevent.cpp
src/corelib/kernel/qcoreevent.h
|