[FFmpeg-devel] [PATCH v2] lavu/opt: Clarify that AVOptions is not indended for general use

[Anton Khirnov]

Quoting Andrew Sayers (2024-04-23 11:51:00)
> On Tue, Apr 23, 2024 at 11:21:27AM +0200, Anton Khirnov wrote:
> > > lavu/opt: Clarify that AVOptions is not indended for general use
> > 
> > They _are_ intended for general use though.
> 
> In that case I'm confused...
> 
> Let's say I make a desktop app to transcode videos.  Obviously I would use
> AVOptions to display configuration options for different encoders.  And it's
> possible to create AVOptions objects for my UI.  But how strongly is that use
> case recommended?
> 
> To provide a particularly difficult example - let's say I want to let the user
> choose between interface themes, and I want to show both some text and a
> picture of the theme.  AVOption doesn't include a "text + picture" option,
> so how would I extend it to meet my needs?

If they fit your use case, then use them, otherwise don't - that's true
for pretty much all APIs we provide.

-- 
Anton Khirnov