From d892dcf1c80a3c597d8cdf894ef431dead3967f8 Mon Sep 17 00:00:00 2001 From: WyattBlue Date: Fri, 3 Nov 2023 02:13:53 -0400 Subject: [PATCH] Remove `flags.txt` This doc file is outdated, hasn't been touched in years, and is not needed for anything. Just remove it. --- flags.txt | 53 ----------------------------------------------------- 1 file changed, 53 deletions(-) delete mode 100644 flags.txt diff --git a/flags.txt b/flags.txt deleted file mode 100644 index a2d730711..000000000 --- a/flags.txt +++ /dev/null @@ -1,53 +0,0 @@ - - -Objects with flags -=== -√ AVCodec.capabilities -√ AVCodecDescriptor.props -√ AVCodecContext.flags and flags2 -AVOutputFormat.flags - - - -Thoughts -=== - -- Having both individual properties AND the flags objects is kinda nice. -- I want lowercase flag/enum names, but to also work with the upper ones for b/c. - - -Option: av.enum flags. - - context.flags2 & 'EXPORT_MVS' - - context.flags2 |= 'EXPORT_MVS' - - new APIs: - - 'export_mvs' in context.flags2 - - context.flags2.export_mvs = True - - context.flags2['export_mvs'] = True - -Option: object which represents all flags, but can't work with integer values - - context.flags merges flags and flags2 - - this is really only handy on AVCodecContext, so... fuckit? - -Option: all exposed as individual properties - - context.export_mvs - - - This polutes the attribute space a lot. - - This feels the most "pythonic". - - If you can set multiple in constructors, then NBD if you want to do many. - - I don't like how I have to pick names. - - - - - -How to name -=== - -If a prefix is required, one of: - - is - - has - - can - - use - - do - -