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
This commit is contained in:
parent
e3fbc7752f
commit
18cbc4ff3d
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user