summaryrefslogtreecommitdiffstats
path: root/src/gui/painting/qblittable.cpp
diff options
context:
space:
mode:
authorHolger Hans Peter Freyther <holger@moiji-mobile.com>2012-01-01 19:58:20 +0100
committerQt by Nokia <qt-info@nokia.com>2012-01-02 10:44:00 +0100
commit3ec27f827e64b4d69f7c6ec7357dc6b03b601fc9 (patch)
tree093aa092bd8c1451adbe823c84609bda2eaa65e8 /src/gui/painting/qblittable.cpp
parent24c88ebcde0d43884303e3238bd068c23135f08b (diff)
blitter: Kill the isBlitterLocked variable of the QBlitterPaintEngine
It starts with being initialized wrongly, the call to buffer() will lock the data while we think it is not locked, it can also get out of sync by someone calling buffer() again. Remove the variable and check with the QBlittable if we need to lock the resource into memory. Change-Id: I350375011138d1b4c2c48c100b7b30b8ea2ae460 Reviewed-by: Jørgen Lind <jorgen.lind@nokia.com>
Diffstat (limited to 'src/gui/painting/qblittable.cpp')
-rw-r--r--src/gui/painting/qblittable.cpp6
1 files changed, 6 insertions, 0 deletions
diff --git a/src/gui/painting/qblittable.cpp b/src/gui/painting/qblittable.cpp
index 11058582ef..fe51f7adb0 100644
--- a/src/gui/painting/qblittable.cpp
+++ b/src/gui/painting/qblittable.cpp
@@ -100,6 +100,12 @@ void QBlittable::unlock()
}
}
+bool QBlittable::isLocked() const
+{
+ Q_D(const QBlittable);
+ return d->locked;
+}
+
QT_END_NAMESPACE
#endif //QT_NO_BLITTABLE