Re: Re: libvo2 api/design problem

Hi,

> Hi,
> 
> > > > I'd prefere #1, but would extend the vo_info_t structure by
> 
> the problem is that no such thing called vo_info_t
> there is now module_t which is common for all module types
> (i didn't like the common info_t thingie, but i ack it's required for
> nice config and plugin management code).

Why not using the flag field? the upper 16 bits could be used for
module specific info? I wouild like this for af as well.

//Anders