| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Needed for Declarative UI integration.
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
test wouldn't finish.
Running under valgrind and slow operating systems, the transfer rate is
only a couple of MB per second. As long as you can reach 3.2 MB/s now,
it should still work
Also, don't kill the thread, for any reason. That causes trouble.
Reviewed-by: Markus Goetz
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The delete reply; was introduced by a conflicted merge in the VxWorks
port. It should not have appeared.
But take this opportunity to convert the two other uses of
QNetworkReply* without lifetime management to QSharedPointer too.
Reviewed-by: Markus Goetz
|
| |
| |
| |
| |
| |
| |
| | |
Autotest: included
Merge-request: 378
Reviewed-by: Eskil Abrahamsen Blomfeldt <eblomfel@trolltech.com>
|
| |
| |
| |
| | |
Reviewed-by: kh
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Text used to be formatted during the parsing of the SVG file, but
because the text can be referenced by a 'use' element, the text
formatting is not known at this point in time. Now, font attributes can
be inherited from 'use' elements, and the text is formatted each time
it is drawn.
Reviewed-by: Tor Arne
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
regression introduced in e43eae35 because the code of maybeParseFunction
and parseFunction is not exactly the same.
Reviewed-by: Kent Hansen
|
| |
| |
| |
| | |
Reviewed-by: Andreas
|
| |
| |
| |
| |
| |
| |
| | |
This method is necessary for QML to support Qt interfaces, but probably
shouldn't be used otherwise.
Reviewed-by: Roberto Raggi
|
| |
| |
| |
| |
| |
| | |
This will be used by the declarative module to optimize property bindings.
Reviewed-by: Roberto Raggi
|
|/
|
|
|
|
| |
This will be used by the declarative module to determine if a property lacking a NOTIFY signal is truly constant, or just missing a NOTIFY signal.
Reviewed-by: Roberto Raggi
|
|
|
|
|
|
|
|
|
|
|
| |
This enables very long failure messages (e.g. including an entire
build log in a failure message).
This change modifies only the plain test logger to use this feature.
Task: 253861
Reviewed-by: Michael Goddard
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
QGLColormap::setEntry() was inserting entries instead of
replacing them; QGLColormap::setEntries() had an incorrect
assert and weird behaviour for the "base".
The documentation for QGLColormap::isEmpty() has been updated
to reflect that it will also report empty if the colormap has
not been set on a QGLWidget even if it has entries in it.
This behaviour is required by existing code.
Reviewed-by: Rohan McGovern
|
|
|
|
| |
Reviewed-by: trustme
|
|
|
|
| |
Reviewed-by: trustme
|
|\ |
|
| |
| |
| |
| |
| |
| | |
being removed.
Reviewed-by: Volker Hilsheimer
|
| | |
|
| | |
|
| |
| |
| |
| | |
Reviewed-by: Peter Hartmann
|
| |
| |
| |
| |
| |
| |
| |
| | |
This makes Qt work on QNX 6.4.
* no q3support, no phonon
* no QSharedMemory, no QSystemSemaphore, no QProcess
Reviewed-By: Robert Griebl
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This makes Qt work on VxWorks 6.6+ in native (kernel) mode.
* compiles with the WindRiver GNU toolchain (Linux only)
* works with QWS (tested with the VNC driver only)
* tested on PPC hardware and the x86 VxWorks simulator
* no q3support, no phonon, no webkit
* no QSharedMemory, no QSystemSemaphore, no QProcess
* only one QApplication instance (flat address space)
* filesystem support depends heavily on the quality of the native driver
* QLibrary is just a dummy to make plugins work at all
* qmake transparently creates VxWorks munching rules for static ctors
* made auto-test cope with missing OS features
A special note regarding the Q_FOREACH patch for dcc:
when calling foreach(a,c) with c being a function returning a container,
the compiler would generate 5 references to some labels (.LXXXX), which
are not there (so the linker complains in the end).
Seems like dcc doesn't really like the 'true ? 0 : <function call to get type>'
statement
Reviewed-By: Harald Fernengel
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change ensures that mouse presses received by the scene when there
are no current mouse grabbers trigger hover event delivery. This is
useful when the scene only receives presses, and no mouse moves (e.g.,
disabling mouse tracking on the viewport, or on systems where the
mouse press is the first received event).
Reviewed-by: Michael Brasser
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Change f68fed3 introduced a few regressions in the QGraphicsWidget
autotests. It turned out those autotests relied on behavior that this
fix "fixed". The exact bugs were 1) that setting focus on a window
or a child of a window that isn't active will automatically give that
item focus, despite that its window is inactive (in contrast it should
just set up subfocus and give the item focus when the window is
activated), and 2) that adding a window to a scene that is active did
not immediately activate that window.
So one fix in the test and one in QGraphicsScene. The autotests were
modified so that the respective tests operate on an active scene (by
assigning the scene to an active view). The change in QGraphicsScene
ensures that the first window that gets added to an active scene that
does not have any active windows already, automatically gets activated.
Reviewed-by: Michael Brasser
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The idea of having separate rotationX/Y/Z, shearX/Y, etc.
methods in QGraphicsItem turned out to be not giving us
the flexibility we need and wanted.
The new code now implements a different scheme, where we
keep simple rotate (around z-axis), scale and
transformOriginPoint methods, but remove the other ones.
Instead we now have an additional list of QGraphicsTransform
object. QGraphicsTransform is an abstract class that inherits
QObject. Several specializations are provided and can be
used to transform (and through property bindings animate)
the item.
Reviewed-By: Andreas
|
| |
| |
| |
| |
| |
| |
| |
| | |
If comparing two variants fails, the failure message will now output
the type and value of the variants (rather than
"Compared values are not the same").
Reviewed-by: Thiago
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
throwing them.
Autotest included.
Task: 258081
Reviewed-by: Trustme
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I added this test because I thought that the compiler would find the
forward-declarations due to the "one definition" rule. In hindsight,
it's not a good idea.
Sun CC warns about this, gcc doesn't. With Sun CC, the code leaks,
with gcc it doesn't.
|
|/ |
|
|
|
|
| |
Reviewed-by: Trustme
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If you set this flag on an item, and descendant item that gains input
focus will become this item's focus proxy. This simplifies how focus
proxy items are assigned from QML; instead of binding the possible
focusProxy property to a named child widget, this assignment happens
automatically as you set the focus property of a descendant to true.
As part of this change, QGraphicsWidget::focusWidget behavior has been
improved and moved into QGraphicsItem. For example, if you set focus on
an item that it's part of a scene, it can gain focus once the parent
has been assigned (which is how object trees are built in QML).
Autotests are included.
Reviewed-by: Michael Brasser
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
No wonder QT_SHAREDPOINTER_TRACK_POINTERS was having no effect:
there was an #include <QtCore/QtCore> before it.
|
|
|
|
| |
This requires modifying slightl QProcess on Unix to forward stdin too.
|
| |
|
|
|
|
|
|
| |
It is possible to export symbols in template classes, but I
don't think we use any such cases now (template specialisation).
It only works properly with C++0x anyway (extern template).
|
| |
|
|
|
|
|
|
|
| |
structure in QSharedPointer""
This restores the original implementation of the creating
function. The next commit will make it suitable for use.
|
| |
|
|
|
|
|
|
| |
and link against a regular Qt build.
Reviewed-by: Trustme
|