| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
We shouldn't fail in our autotests because the platform is buggy. But
note the problem. We should report the bugs upstream...
|
|
|
|
|
| |
The license header update in e12a03d5 changed the .ui templates, but
not the baselines in all cases.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of storing whether or not our clip is dirty and updating it in
every paint operation we'll just update it whenever it changes. This is
more intuitive and should be faster for the common case as well.
Also make sure to implement clip(region).
Prevent multiple updateClip() calls for a single clip operation by
introducing a flag to check whether we recursed into the different
clip() calls.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
|
|
| |
Make sure to call CLIPPED_PAINT so painting with a region clip works.
Reviewed-by: Donald <qt-info@nokia.com>
|
|
|
|
| |
Same as in the bookmarks example.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the function a bit more useful, since previously it was only
safe to use if you were sure that it would not encounter an unexpected
child element, or if you would be alright with canceling the parser on
such an occurrence.
Now it is also possible to have it ignore any unexpected child elements,
or to have it include the text found in any child elements.
Task-number: 231938
Reviewed-by: mae
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QXmlStreamReader::readNextStartElement reads until the next start
element within the current element, or returns false when no such
element is encountered before the end element is reached. It simplifies
the common case of iterating over the elements in an XML document.
QXmlStreamReader::skipCurrentElement reads until the end element of the
current element, skipping any child elements. This functionality was
requested in two tasks, and a similar function 'readUnknownElement' was
present in Qt's stream reader example.
Autotest is included, example and documentation have been updated.
Task-number: 238793
Reviewed-by: mae
|
|
|
|
| |
Reviewed-by: Olivier
|
|
|
|
| |
autotest will detect the problem
|
|
|
|
| |
Reviewed-by: Marius Storm-Olsen
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QRasterPaintEngine::drawImage() used an optimized code path when the
source rectangle was 1x1. It would sample the source image at the
source rectangle's top-left corner and use the sampled color to fill
the entire target rectangle. There were two bugs, however:
1) The sampled color was assumed to be non-premultiplied, so you could
end up with premultiplying the color twice. This was fixed by
avoiding premultiplying a second time if the source image has a
premultiplied format.
2) Since the source rectangle is a QRectF, it could easily cross pixel
boundaries even if it's 1x1. In this case, it is not correct to fill
the target rectangle with a single color. This was fixed by checking
if the entire source rectangle is contained in a single pixel before
taking the optimized code path.
Task-number: 256950
Reviewed-by: Trond
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
We don't need to chain to the base class since the QDirectFBScreenCursor
always is rendered by hardware but we should update the pos variable in
case people ask where the cursor is.
Reviewed-by: TrustMe
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Removed the reference to the QAnimationState that doesn't exist anymore
|
| |
| |
| |
| |
| |
| |
| |
| | |
The problem is that headers in QTestLib define functions for mouse
and key events. Those are causing link errors on all autotests
that do "QT -= gui" with mingw (only debug seems to be affected).
Reviewed-by: jasplin
|
| |
| |
| |
| |
| |
| |
| | |
XRectangle coordinates need to be clipped to the short integer range.
Task-number: 250137
Reviewed-by: Trond
|
| | |
|
| |
| |
| |
| | |
where it breaks, so let's find out where.
|
| | |
|
| |
| |
| |
| |
| |
| | |
we needed to finalize the selection when rows are removed
Reviewed-by: ogoffart
|
| |
| |
| |
| |
| |
| |
| | |
dataChanged is emitted with invalid model index. We needed to handle
that.
Reviewed-by: ogoffart
|
| |
| |
| |
| | |
Gestures only awailable on 10.6
|
| | |
|
| |
| |
| |
| | |
Reviewed-By: Samuel
|
| |
| |
| |
| |
| |
| |
| |
| | |
The QTableView scrolled down after the sections swap.
Setting the current index to the topmost visual element fixes the issue.
Reviewed-by: Thierry
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Some X servers seem to report zero physical size, so our DPI
calculations would crash with divide-by-zero. Avoid this and just use
72 DPI instead.
Task-number: 258319
|
| |\ |
|
| | | |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | | |
Reviewed-by: Sarah Smith
|
| | |/
| |/|
| | |
| | | |
Reviewed-by: Gareth Pethig
|
| | |
| | |
| | |
| | | |
Reviewed-by: Trust Me
|
| | |
| | |
| | |
| | | |
Reviewed-by: Trust Me
|
| |/
| |
| |
| |
| |
| |
| | |
qmake -tp vc (rightfully) borks when it tries to include .pros that
it shouldn't be, based upon platform.
Reviewed-by: Rohan McGovern
|
| |
| |
| |
| |
| |
| |
| | |
After 843d2eed0ac10589a01d40bfdf88cb44c6a00b17 qmake didn't compile
anymore.
Reviewed-by: TrustMe
|
| |
| |
| |
| |
| |
| |
| |
| | |
When we have proper window manager support from DirectFB we shouldn't
create our own primary surface. This patch vastly cleans up a number of
issues in QDirectFBScreen regarding this.
Reviewed-by: Donald <qt-info@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
Make QT_DIRECTFB_WM be defined if QT_NO_DIRECTFB_WM is not. This makes
it possible to write more readable code.
Reviewed-by: Donald <qt-info@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
To avoid confusion rename QDirectFBScreen::dfbSurface()
primarySurface() since this is what it is.
Reviewed-by: Donald <qt-info@nokia.com>
|
| |
| |
| |
| |
| |
| |
| | |
Make sure we recreate the paint engine if it's 0 in beginPaint. Also
don't delete the paint engine in moves, only resizes.
Reviewed-by: Donald <qt-info@nokia.com>
|
| | |
|
| |
| |
| |
| |
| | |
only one of yyIdent, yyComment and yyString is used at a time, so use a
common yyWord instead
|
| |
| |
| |
| |
| | |
compare with pre-initialized qstrings instead of qlatin1strings. that
way the length is known in advance.
|
| |
| |
| |
| | |
work more with raw data instead of qstring functions
|