4dd89c6903
which supports ReadLockWithTimeout() * commented the code in many more places * understood the problem of making the read/write locking work: While it would be possible for each window to remove the processed region from the global dirty region in read lock mode (since it is guaranteed not remove a region not intersecting with its own visible region), multiple window threads can still not do this at the same time, since BRegion itself is not threadsafe of course. * I need to figure out a way for the window threads to be able to access and modify all needed data in read only mode, I think this means to divide the global dirty region into each window again, so that each window thread can simply clear its own dirty region instead of excluding it from the global region. Yeah, that might work. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@15230 a95241bf-73f2-0310-859d-f6bbb57e9c96 |
||
|---|---|---|
| .. | ||
| add-ons | ||
| apps | ||
| bin | ||
| kernel | ||
| kits | ||
| misc | ||
| servers | ||
| ExampleTest.cpp | ||
| ExampleTest.h | ||
| ExampleTestAddon.cpp | ||
| Jamfile | ||
| UnitTester.cpp | ||
| UnitTester.h | ||
| UnitTester.rsrc | ||