| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
Some of the platform test infrastructure assumes that all unit
tests are sub-directories under tests/auto, and the tests/auto/math3d
sub-directory was confusing that infrastructure.
Reviewed-by: trustme
|
| | |
|
| | |
|
| |
|
|
|
| |
The change of URLs in Qt broke the tests that operated on URLs. This
wasn't properly done, so revert to the last working values.
|
| |
|
|
|
| |
We won't fix any issues in those libraries anyway, so don't waste time
checking.
|
| |
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
| |
where it breaks, so let's find out where.
|
| | |
|
| |
|
|
|
|
|
|
| |
The QTableView scrolled down after the sections swap.
Setting the current index to the topmost visual element fixes the issue.
Reviewed-by: Thierry
|
| |
|
|
|
|
|
| |
qmake -tp vc (rightfully) borks when it tries to include .pros that
it shouldn't be, based upon platform.
Reviewed-by: Rohan McGovern
|
| |
|
|
|
|
|
|
| |
remove all c++ code which is not part of the critical test data. as a
result, remove the license headers where the remaining text cannot be
reasonably considered copyright-worthy any more.
this is a somewhat persistent solution to the ever-changing license
headers screwing up the tests.
|
| |
|
|
| |
Reviewed-by: ogoffart
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The orientation tag was ignored for tiff images. The tag is now used
to rotate the image before providing it to the user.
The orientation of indexed an mono images is done completely manually.
The orientation of other type is done in conjunction to the mirroring
already performed by libtiff.
Task-number: 258526
Reviewed-by: Samuel Rødal
|
| |
|
|
|
|
|
|
|
|
|
|
| |
New flag: QGraphicsItem::ItemNegativeZStacksBehindParent, which makes
it easy to toggle stack-behind based on the value of Z alone.
Add interface initializations to QGV classes.
Add a simple internal focus policy to QGraphicsItem to allow derived
items to be focusable without allowing clickfocus.
Reviewed-by: Alexis
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
setTransformationAnchor(QGraphicsView::AnchorUnderMouse) would not work
properly if viewport margins were set. When centering the view in
QGraphicsViewPrivate::centerView, the viewport margins were not being taken
into account.
Mapping from global cursor coordinates in the viewport instead of the view
fixes the issue.
Task-number: 255529
Reviewed-by: Olivier
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We set the document's page size to be large enough to contain an
image which is 100 pixels wide and one, but not two, instances of the
word 'Foobar'. We then render HTML which contains a string with repeated
occurrences of the word 'Foobar' next to a floating, right-aligned image
which is 100 pixels wide. The layout should break on word boundaries,
since this is the default in QTextDocument, and thus each text line
should contain one instance of the word 'Foobar'.
Task-number: 240325
|
| |
|
|
|
|
|
|
|
| |
This enables the use of Q_DECLARE_SHARED with d-pointers that are
QExplicitlySharedDataPointer<PrivateClass>.
Also, this enables swapping atomically QSharedPointers.
Reviewed-by: Harald Fernengel
|
| |
|
|
|
|
|
| |
Previously we only checked headers, but we actually care about source
files too. This detects about 50 errors all over Qt.
Discussed with Thiago.
|
| |
|
|
| |
Reviewed-by: trustme
|
| |
|
|
| |
"sm"+ellipsis (...) is same length as "small" in some fonts
|
| | |
|
| |
|
|
|
|
| |
Handle platforms that don't have backends.
Reviewed-by: Bill King
|
| | |
|
| |
|
|
| |
tst_qobject deleteQObjectWhenDeletingEvent needs QtGui.
|
| | |
|
| |
|
|
|
| |
Task-number: 214990
Reviewed-by: Joerg
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change would have been much simpler if either QGraphicsItem
inherited QObject, or if we had some similar QPointer-like class that
supported QGraphicsItem. The issue is this: Each item can delegate
another item to be its focus proxy. That item can be a parent or child,
or something completely unrelated. Either of the two items can be
deleted independently.
The former solution was to store backpointers in a map in the scene.
Problem is, the items may not be in a scene when this happens, they
may be removed from the scene, and the items may be moved between
two scenes.
The bad part about this fix is that it adds another pointer to
QGraphicsItemPrivate.
Reviewed-by: Shane Kearns <shane.kearns@sosco.com>
|
| | |
|
| |
|
|
|
| |
Mac needs a bit more time to update the widgets when they
are redocked
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When specifying round corners with QStyleSheetStyle and no border-width
specified, the round corners were not rendered with antialiasing. Furthermore,
if border-width was set to 0, part of the border was rendered in discordance
with CSS3.
The background in now rendered directly instead of drawing a clipped
rectangle. The actual border width is checked before rendering.
A test has been added at tests/auto/uiloader/baseline/css_borderradius_allwidgets.ui
Task-number: 230362
Reviewed-by: olivier
|
| |
|
|
|
| |
Since QTouchEvents can also be sent to QGraphicsItems, we want to test
that it actually works.
|
| | |
|
| |
|
|
| |
Reviewed-by: mauricek
|
| |
|
|
|
|
| |
It is now possible to set a start value and no end value and starting
the animation will pick the default end value from the current value
of the property that's being animated.
|
| |
|
|
|
|
|
|
| |
You can now also set the axis following hte Qt::Axis enum
Note: I'm not 100% sure about the maths in QGraphicsRotation::applyTo
Feel free to fix it.
Reviewed-by: ogoffart
|
| |\ |
|
| | |
| |
| |
| | |
This test only works in debug mode
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The problem was that we were locking a mutex that was global to thread
to remove posted events associated with a QObject from the posted event
list. We were also immediately deleting those events. If that triggers
the deletion of another QObject, you would then trigger a dead-lock.
Task-number: 259514
Reviewed-by: brad
Reviewed-by: ogoffart
|
| |/
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: Trust Me
|
| |
|
|
| |
Reviewed-by: Trust Me
|
