On 6/14/07, Chris Bore <[EMAIL PROTECTED]> wrote: > Should it be recommended that a 'user' of DirectFB should never use the > Surface data pointer, but should instead access that data only through the > Surface interface methods?
Are you talking about the priv pointer? Anything accessed through priv is subject to change, so using that pointer means your application will likely break when you update your version of DirectFB. If you're talking about the pointer you get when you do a Lock() operation -- that's part of the documented interface. As long as you Unlock the surface and stop use of the data pointer while it's unlocked, you should be OK, although depending on the hardware, using the surface methods may be a lot faster than reading or writing from the surface's memory. _______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users