FYI: The IDirectFBSurface interface's Lock and Unlock functions are a standard part of the DirectFB API (they are fully supported and do not bypass any critical functionality). They work well IMHO if one wants to party with the pixels, especially on UMA based architectures where there is no distinction between system and video memory.
Procedural textures/images and modifications are well suited to such an approach, of depending on your platform using a video memory based surface might be helpful for improved performance. Cheers, Timothy -- Timothy Strelchun CE Software Engineering Digital Home Group Intel Corporation >Date: Thu, 23 Dec 2010 09:12:48 +0000 (GMT) >From: Chris Bore <chris_b...@yahoo.co.uk> >Subject: Re: [directfb-users] accessing the row >To: ravi <ravi...@gmail.com>, Sriram Neelakandan > <sriram.neelakan...@gmail.com> >Cc: directfb-users@directfb.org >Message-ID: <219581.42647...@web27007.mail.ukl.yahoo.com> >Content-Type: text/plain; charset="utf-8" > >Although it is used in DirectFB, I do not recommend using the >Lock/Unlock functions. They bypass the API, and raise other >issues that can be problematic. >I do not think there is ever a case where using Lock to gain >direct access to the encapsulated pixel data is really >necessary - it can always be done using the standard API. If >you explain what you are trying to do then perhaps I can >suggest another way to do it. > ================================== >Chris Bore >Training Director >BORES Signal Processing >ch...@bores.com >www.bores.com >+44 (0)1483 740138 _______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
