Allow inputs to say they cannot support mipmaps.
authorSteinar H. Gunderson <sgunderson@bigfoot.com>
Tue, 28 Jul 2015 23:28:30 +0000 (01:28 +0200)
committerSteinar H. Gunderson <sgunderson@bigfoot.com>
Tue, 28 Jul 2015 23:28:30 +0000 (01:28 +0200)
commitbff07c51f937a4fdf005d31ef7e064467db67511
tree7ea790d406b03a45a50e1e2821ed0d8fdde61d53
parent61e2a7671f7b22227dcdc34dd303ae4fcc802aaa
Allow inputs to say they cannot support mipmaps.

Really only FlatInput can easily support mipmaps; for things like YCbCrInput
that combine multiple inputs, it's hard (probably not downright impossible,
but at least not immediately obvious without thinking about it a bit) and for
FFTInput it makes no sense.

Thus, we allow an input to say that it can't do this, and then bounce it
to a texture if needed. Hopefully this should happen quite rarely.
effect_chain.cpp
effect_chain.h
effect_chain_test.cpp
fft_input.h
input.h
ycbcr_input.cpp
ycbcr_input.h
ycbcr_input_test.cpp