Calvin Williamson wrote:
Right. And between scanline calls, the ScanlineProcessor walks
the lists of input and output data, and for any ImageData objects
it finds, it gets the iterator from that ImageData object and
then advances it to the next line.
Its better to pass the whole lists of input and output
data objects (just like in prepare, process, finish) to the
subclass of op, since that is where other inputs (eg like
scalars or whatever) will be stored as well. (It doesnt
work that way yet though...)
Calvin
Alright.
Will there be other kinds of iterators in the future? E.g. will there
be a sliding-neighborhood iterator, or whole tile iterator? And if so,
should an ImageOp be allowed to have more than one iterator associated
with it at the same time?
Also, you mention that the instantiated op "knows" what order it's data
inputs and outputs are in. How does it know that?
--
Daniel
