Allow image providers to force their loading to be asynchronous

The request methods of an image provider are assumed to be synchronous,
but sometimes the provider will be implemented in an async manner, eg.
through network request or doing the I/O on a different thread. In that
case, the provider can't expose this async behavior to clients, but needs
to block in the request method. This is less then ideal for clients,
since the default behvior of an image element is to load synchronously,
so we introduce a new flag to image providers that let's the provider
force the loading to happen on the async image loading thread.

Similar to network requests (which are always async), this does not
affect the 'asynchronous' property of the image element.

Change-Id: I9542abbcc594b9aab565210bc3005a95592c1e9c
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@nokia.com>
Reviewed-by: Michalina Ziemba <michalina.ziemba@nokia.com>

1 files changed, 7 insertions, 0 deletions

diff --git a/src/qml/qml/qqmlengine.h b/src/qml/qml/qqmlengine.h
index 8d250ed209..8640f1acad 100644
--- a/src/qml/qml/qqmlengine.h
+++ b/src/qml/qml/qqmlengine.h
@@ -64,14 +64,21 @@ public:
         Invalid
     };
 
+    enum Flag {
+        ForceAsynchronousImageLoading  = 0x01
+    };
+    Q_DECLARE_FLAGS(Flags, Flag)
+
     virtual ~QQmlImageProviderBase();
 
     virtual ImageType imageType() const = 0;
+    virtual Flags flags() const = 0;
 
 private:
     friend class QQuickImageProvider;
     QQmlImageProviderBase();
 };
+Q_DECLARE_OPERATORS_FOR_FLAGS(QQmlImageProviderBase::Flags)
 
 class QQmlComponent;
 class QQmlEnginePrivate;