From db5aad6a99996b134cb406dc562017690f6a6812 Mon Sep 17 00:00:00 2001 From: Gunnar Sletta Date: Thu, 30 Jun 2011 10:43:31 +0200 Subject: [PATCH] Document threading issues with QSGEngine signals Change-Id: I769c0793929c4c90464f6e9fea46bd1a19fbacf3 Reviewed-on: http://codereview.qt.nokia.com/939 Reviewed-by: Qt Sanity Bot Reviewed-by: Gunnar Sletta --- src/declarative/scenegraph/util/qsgengine.cpp | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/src/declarative/scenegraph/util/qsgengine.cpp b/src/declarative/scenegraph/util/qsgengine.cpp index 1b7f058..9714749 100644 --- a/src/declarative/scenegraph/util/qsgengine.cpp +++ b/src/declarative/scenegraph/util/qsgengine.cpp @@ -113,6 +113,10 @@ QSGEngine::~QSGEngine() The GL context used for rendering the scene graph will be bound at this point. + + Since this signal is emitted from the scene graph rendering thread, the receiver should + be on the scene graph thread or the connection should be Qt::DirectConnection. + */ /*! @@ -124,6 +128,9 @@ QSGEngine::~QSGEngine() or to do screen scraping of the current frame buffer. The GL context used for rendering the scene graph will be bound at this point. + + Since this signal is emitted from the scene graph rendering thread, the receiver should + be on the scene graph thread or the connection should be Qt::DirectConnection. */ -- 1.7.2.5