If we treat a DirectFB Surface as an object, accessed through its interfaces, then we would not want to directly access any of the internal data that object contains? That is, you should access the data of an object only through the methods of the interfaces that object provides.
But a DirectFB Surface does provide a data pointer, which a programmer could use to directly access the internal data. 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? (I can see that a developer, say of a new ImageProvider, could find it useful to be able to access the data buffer directly - provided that the data buffer does map in a standard way - but I think that is working to add to DirectFB rather than to 'use' it, so the violation is permissible.) Thanks ======================== Chris Bore BORES Signal Processing [EMAIL PROTECTED] www.bores.com Tel: +44 1483 740138 Mobile: +44 7921 153 219 _______________________________________________ directfb-users mailing list directfb-users@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
