Hmm their is no public concept of a interface with inheritance.
It may be time to consider adding this.


On 3/9/07, Denis Oliver Kropp <[EMAIL PROTECTED]> wrote:
> Daniel Laird schrieb:
> > On this subject (well related anyway)
> >
> > I am currently working on a number of patches that can be applied to
> > mainline Directfb.  They are currently in use internally.
> > One of the patch sets I am looking to submit is the use of events for
> > VideoProviders so a DFBVideoProviderEvent.
> > This will allow events to be passed as they happen in a Live Video Stream.
> > This is very important for us as we are using a Hardware Video Decoder and
> > it will decode things like Aspect Ratio Changes in the Video or to detect
> > video fomat changes where broadcasters change the video encoding format.
> > Using evets will allow signalling of applications built on top of DirectFB.
>
> Of course, I forgot to mention the video provider events :)
>
> > Adding this kind of event to layers as well would probably we really useful
> > as well.
>
> With the number of event providing interfaces growing from two
> (window/inputdevice) to five (win/input/video/layer/surface),
> should we avoid duplication of the three event buffer related
> methods in each interface? Ideas?
>
> --
> Best regards,
>    Denis Oliver Kropp
>
> .------------------------------------------.
> | DirectFB - Hardware accelerated graphics |
> | http://www.directfb.org/                 |
> "------------------------------------------"
>
> _______________________________________________
> directfb-dev mailing list
> [email protected]
> http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
>

_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to