From 18cbc4ff3d251beeba54f148a22e090ad741dd60 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stephan=20A=C3=9Fmus?= Date: Sat, 25 Jun 2005 22:56:24 +0000 Subject: [PATCH] Using the read locking in DisplayDriver was a bit early. Painter itself is not thread safe, so while we use the HWInterface lock for locking, we can only do read locking once each window has its own Painter instance. I'm still investigating this possibility. It depends on the memory foot print of painter, of which I don't have a clear idea yet. Anyways, this quick change fixes Adis problems and is required at this time anyways. Sorry for the inconvenience. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@13278 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- src/servers/app/drawing/DisplayDriverPainter.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/servers/app/drawing/DisplayDriverPainter.cpp b/src/servers/app/drawing/DisplayDriverPainter.cpp index 2170c13b5b..7c1a33c90b 100644 --- a/src/servers/app/drawing/DisplayDriverPainter.cpp +++ b/src/servers/app/drawing/DisplayDriverPainter.cpp @@ -1065,14 +1065,14 @@ DisplayDriverPainter::StringHeight(const char *string, int32 length, bool DisplayDriverPainter::Lock() { - return fGraphicsCard->ReadLock(); + return fGraphicsCard->WriteLock(); } // Unlock void DisplayDriverPainter::Unlock() { - fGraphicsCard->ReadUnlock(); + fGraphicsCard->WriteUnlock(); } // WriteLock