Re: Caps and Options update

[Guillaume Emont <gemont igalia com>]

On 05/04/2011 11:30, Iago Toral wrote:
> Now, in general I think of caps more like TRUE/FALSE properties telling
> if certain capability is supported by the source or not, in that case
> FALSE should be the default if a particular cap does not exist (== is
> not supported)
> 
> In case we do need caps with values other than a gboolean, then I'd have
> the get APIs return a gboolean as you suggest above.

For consistency, I'd rather always return a gboolean saying whether the
capability was set, and pass the value through an (out) argument.