Hi Denis, >> 3. There is no way to simultaneously obtain IDirectFBSurface >interface >> pointers for each of the three buffers. > >The interface is for all buffers at once, you cannot directly get an >interface for a specific buffer. Do you need that for (hardware) video >decoding?
No, I am just inquiring to verify understanding. However, related to IDirectFBVideoProvider::PlayTo() requiring a surface, I am considering creating a pseudo/virtual surface for a layer to expose (when the layer is setup to use a non-surface based hardware accelerated video source) to establish the link between the video provider and the associated layer. Does that make sense from a DirectFB architectural perspective and fit intended usage of non-surface based sources? (Feel free to move this discussion to the dev list if you wish) >I'm planning to add support for buffer indices for these methods: > >FlipTo( index ) >GetFramebufferOffset( index ) >LockBuffer( index ) > >The names are not final. These sound useful/flexible and would allow the user to potentially skip displaying a frame that maybe is too-old due to a system hiccup or something. Personally, I like having the control of being able to flip to an exact surface (and not requiring them to necessarily be in a surface chain), but of course that does complicate API usage for newbies. Regards, Timothy -- Timothy Strelchun CE Software Engineering Digital Home Group Intel Corporation The views expressed above are my own and not those of Intel _______________________________________________ directfb-users mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
