| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
QTextControl has two independent interaction flags
TextEditable and TextSelectableByKeyboard, i.e. the latter can also
apply in read-only mode. This used to be handled incorrectly
in QTextEdit.
Reviewed-by: con
|
|
|
|
|
|
|
|
|
| |
QTextControl has two independent interaction flags
TextEditable and TextSelectableByKeyboard, i.e. the latter can also
apply in read-only mode. This used to be handled incorrectly
in QPlainTextEdit.
Reviewed-by: con
|
|
|
|
| |
The variable updatesEnabled is not used on Mac OS X.
|
|
|
|
|
|
|
|
| |
Setting a pixmap brush when painting to a 32-bit target might cause the
source pixmap to be converted to 32-bit. We should detach the pixmap if
we need to convert it.
Reviewed-by: Trond
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The reason for the crash was the following: When we make menu entries
in Qt, we assign each item an arbitrary command ID. This is because
Symbian usually puts the items in a resource file and refers to them
by ID, but we need to be dynamic. These command IDs are also assigned
to cascading menu items (sub menus). When we then get a callback in
RestoreMenuL with one of submenu IDs, we used to ask Symbian to
construct the menu items for them, but Symbian doesn't know about
them.
Fixed by avoiding call into S60 code if the ID belongs to Qt.
Also put a cap on the number of menu items. It's very unlikely that
anyone will reach it, but it's better to have an actual check.
Task: QT-646
AutoTest: Manual testing went fine
RevBy: mread
|
| |
|
| |
|
|
|
|
| |
RevBy: Trust me
|
|
|
|
|
|
|
|
|
| |
QTextControl showed inconsistent behaviour with DeleteEndOfWord and
DeleteStartOfWord when the cursor had a selection. With this patch,
the commands will simply delete the existing selection, which is
consistent behaviour with in other IDEs.
Reviewed-by: Simon Hausmann
|
|
|
|
|
|
|
| |
The test tst_QListView::task254449_draggingItemToNegativeCoordinates was failing
in cocoa because of this. (on, cocoa, the call to show was doing the first paintEvent)
Reviewed-by: Thierry
|
|
|
|
| |
Reviewed-by: Bjoern Erik Nilsen
|
|
|
|
|
|
|
|
|
|
|
|
| |
When setting a large font using style sheets, the whats this
popup size calculation would be incorrect resulting in
half visible lables. By calling ensurePolished before showing the
label, we ensure that this will be properly handled.
We also added a new test case for whatsThis in tst_qtooltip
Task-number: QTBUG-2416
Reviewed-by: ogoffart
|
|
|
|
|
|
|
|
| |
Greatly improves performance in flush() for the non-MITSHM case on
16-bit displays. Instead of converting the whole image to a pixmap only
convert the sub-rect that's needed.
Reviewed-by: Gunnar
|
|
|
|
| |
Reviewed-by: Gunnar
|
|
|
|
| |
Reviewed-by: Gunnar
|
|
|
|
|
| |
Merge-request: 1541
Reviewed-by: Thiago Macieira <thiago.macieira@nokia.com>
|
|
|
|
|
|
|
|
| |
Change authored by Rhys.
Bug introduced by the change to allow user-specific cache and pipe
directories.
Reviewed-by: Jeremy
|
|
|
|
| |
Reviewed-by:TrustMe
|
|
|
|
|
|
|
|
|
| |
We reuse tooltip whenever we can. But we forget to check if
the format of the text changes inbetween (from html to plain).
This causes the word wrap to fail sometimes. This change will
fix that.
Rev-By:MortenS
|
|
|
|
|
|
|
|
|
|
|
| |
QStateMachine framework installs QObject event filters to catch events
in order to triggers the proper transition. But installing a QObject event
filter on a QGraphicsObject gives nothing because QGraphicsView events
filters works differently. In order to make this works we now post
events using QApplication::postEvent in addition to the QGraphicsView
events.
Reviewed-by:andreas
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When rendering etched text on disabled rich text labels
we would previously draw distorted links.
This is basically because anything that
did not render with the text foreground role would
be drawn twice as a shadow. Since there is no way to properly
render this text etched we will rather disable it completely
when the label uses rich text.
Task-number: QTBUG-4543
Reviewed-by: Simon Hausmann
|
|
|
|
|
|
|
|
|
|
|
|
| |
It wasn't possible for the paint engine to override the drop
shadow filter because QPixmapDropShadowFilter::draw() was not
asking for an engine-specific filter object.
Also, change the OpenVG filter to use vgGaussianBlur() instead of
vgConvolve(), and draw the original image on top of the shadow.
Task-number: QTBUG-4583
Reviewed-by: trustme
|
| |
|
|
|
|
| |
Not sure why the migration classes should be are \obsolete.
|
|
|
|
|
| |
Mark QGraphicsAnchor::unsetSpacing as reset function of the spacing
property.
|
| |
|
|
|
|
| |
Reviewed-by: Trond
|
|
|
|
|
|
|
|
|
| |
This is internal API.
It's possible to specify a horizontal and vertical scale, rotation,
opacity and source rectangle for each pixmap item.
Useful for particle effects.
Reviewed-by: Trond
|
|
|
|
| |
New API will most likely not be in the Beta release.
|
|
|
|
|
|
| |
Seems like I forgot to handle page scrolls.
Also did a small optimization
(see also 45f095b8970dc3c1b6f6e97fa2323654ba848288)
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
It turns out that we need to let singleStep keep its value
in qtextedit so that pushing the up/down buttons on the slider
works as they should. Moreover, overriding the behaviour in
abstract slider also makes QGraphicsView work out of the box.
Also added in the test fix suggested by Olivier.
|
| |
| |
| |
| |
| |
| |
| | |
Stretch, Repeat and Round are too generic. Renamed to StretchTile,
RepeatTile and RoundTile.
Reviewed-by: Gunnar
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This turns the changes in 072e748adbdab1d51b240b9983ce82b213b66f18 off
by default. Define QT_PRIVATE_QWS to turn them on. This must be done for
both qvfb (X11 build) and libQtGui (QWS build). Failure to do so will result
in an inability for applications to communicate with the server.
Task-number: QTBUG-1711
Reviewed-by: Paul
|
| |
| |
| |
| |
| |
| |
| | |
The change implements the same logic for QLabel which QLineEdit (and
implicitely QSpinBox and QComboBox) already had.
Reviewed-by: Simon Hausmann
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Needed when a list or tree supports both moving and copying, but moving
should be the default (e.g. tree of bookmarks, or any other item that
doesn't really make sense being copied in general, but moved often).
Merge-request: 1668
Reviewed-by: Olivier Goffart <ogoffart@trolltech.com>
Reviewed-by: Thierry
|
| |\ \
| | |/ |
|
| | |\
| | | |
| | | |
| | | |
| | | | |
Conflicts:
src/gui/kernel/qwidget_s60.cpp
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Remove all references to "elevation" and how items are sorted by their
"z order". Now use "stacking order" and only refer to "z-value" when
discussing sibling order. Move almost all sorting docs from the
QGraphicsItem::setZValue() function to a general overview section in
QGraphicsItem's class documentation.
Reviewed-by: David Boddie
|
| | | | |
|
| | |\ \
| | | | |
| | | | |
| | | | | |
mmfphonon
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
child widgets
The implementation of QSymbianControl::Draw previously assumed that the co-ordinate system of the control always matched that of the backing store - in other words, that the only widget for which a QSymbianControl was created would be the top-level widget. Now that create_sys has been modified to create a native window (and therefore a QSymbianControl) for child widgets on which winId() is called, this assumption is no longer valid. This function has therefore been modified to map the redraw rectangle into the coordinate system of the backing store.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
already-visible widget
If a widget is visible when winId() is called on it, this change means that the newly-created native window will be activated immediately.
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reviewed-by: Eskil
|
| | | | |
| | | | |
| | | | |
| | | | | |
Reviewed-by: Samuel
|
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
QFileDialog contains own internal derived classes for line edit and
list view. Unfortunately, these classes do not handle keypad navigation
correctly - they just accept the navigation key events, causing the
navigation to halt.
Added support for QFileDialogListView, QFileDialogTreeView and
private filedialog class QFileDialogPrivate to handle and possibly ignore
keypad navigaion key events.
Additionally, added support to keypad navigation to ignore empty
widgets. This allows keypad navigation not to go invisible when empty
widgets are tried to be navigated into.
Task-number: QT-643
Reviewed-by: Alessandro Portale
|
|\ \ \ \ |
|