New commits:
http://git.directfb.org/?p=core/DirectFB.git;a=commit;h=b417724db62384eba84c481c6c7f670f4347a295
commit b417724db62384eba84c481c6c7f670f4347a295
Author: Denis Oliver Kropp <[EMAIL PROTECTED]>
Date: Fri Feb 22 21:08:59 2008 +0100
[surface core] Hotfix failing assumption that flags would still be set when
unlocking.
While locking the surface and managing interlocks, only clear access flags
when the
buffer has not been locked before. Probably we should have an allocation
lock counter.
But it needs to be protected anyhow, e.g. using FusionRef, but I'd like to
avoid overhead
and instead add an allocation manager per Fusionee. This one would just
have one FusionRef,
e.g. as a FusionObject, and a list of locked allocations. The destructor
handles them all.
Another important job for the local allocation manager would be to remember
allocations that
have been attached to locally, e.g. mapped, and require to be detached by
everyone when destroyed.
The XShmImages in the X11 backend are currently only shmat()ed by slave
processes :-P
src/core/surface_buffer.c | 19 ++++++++++++-------
1 files changed, 12 insertions(+), 7 deletions(-)
_______________________________________________
directfb-cvs mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-cvs
