| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Task-number: QT-3957
reviewed-by: Aaron Kennedy
|
|
|
|
| |
QTBUG-13345
|
|
|
|
| |
QTBUG-12729
|
|
|
|
| |
QTBUG-12590
|
|
|
|
|
|
|
| |
invalid timers).
Authored-by: Daniel Molkentin
Reviewed-by: Marco Bubke
|
|
|
|
|
|
|
| |
i.e. the thread with the QNAM the original reply was created in.
Task-number: QTBUG-12302
Reviewed-by: Aaron Kennedy
|
|
|
|
|
| |
(should be handled by image providers, elements shouldn't have to know
about the capabilities)
|
|
|
|
| |
QTBUG-11954
|
|
|
|
|
|
|
|
|
|
| |
synchronous loading of QImages. (QPixmaps can only be created in the
main thread so they will always be loaded synchronously).
This changes request() to requestImage() and adds requestPixmap()
for pixmap support.
Task-number: QTBUG-11989
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The QDeclarativePixmapCache was both slow, and very trickey to use correctly.
Many QML elements did not correctly cancel outstanding requests, which leads
to pixmaps leaking indefinately. Other elements, such as Text, were
subject to race conditions that meant they may never actually load all their
images.
QDeclarativePixmap is a single class than encapsulates the action of
fetching a pixmap, as well as the pixmap itself and the responsibility of
canceling outstanding requests. Rather than relying on Qt's pixmap cache
that doesn't cache all the information QML needs, QDeclarativePixmap
implements its own cache, that correctly degrades over time (unlike
QPixmapCache that can stop expiring items in some conditions).
Reviewed-by: Warwick Allison
|
|
|
|
| |
Task-number: QTBUG-11827
|
|
|
|
| |
Task-number: QTBUG-11645
|
| |
|
|
|
|
|
|
| |
enough.
Work around QTBUG-10622
|
| |
|
| |
|
|
|
|
| |
Task-number: QTBUG-9908
|
|
|
|
| |
We only support Qt 4.7 now.
|
|
|
|
|
| |
Always use private/. The WinSCW compiler doesn't search the current
directory, for whatever reason.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change to Thiago's method:
QThread::quit() is *not* thread-safe, so we mustn't call it from
outside the QThread that the QThread holds. Unlike other QObjects,
this method and some others must not be called from the thread they
have affinity to.
So add a hack to call it in the auxiliary thread. Do that by
connecting a dummy QObject's destroyed() signal to the quit() slot in
a DirectConnection, then move the object to the thread. When we call
deleteLater(), this will cause the thread's event loop to delete the
object, which in turn calls quit() in the actual thread.
Reviewed-by: Thiago Macieira
|
|
|
|
| |
Task-number: QTBUG-8984
|
|
|
|
|
| |
Prevents deadlock on shutdown for very shortlived runs,
e.g. autotests
|
|
|
|
| |
(fixes test too)
|
|
|
|
| |
Task-number: QTBUG-9032
|
|
|
|
|
|
|
| |
Add Translate transform.
Image::sourceWidth and Image::sourceHeight read/write properties.
Task-number: QTBUG-8984
|
| |
|
|
|
|
| |
Task-number: QTBUG-7515
|
|
|
|
|
| |
Allows loading/decoding local images in an asynchronous thread (already
the case for network images).
|
|
QDeclarativeXXX.
|