<br><div class="gmail_quote">On Thu, Aug 13, 2009 at 1:14 AM, Karthik Krishnan <span dir="ltr"><<a href="mailto:karthik.krishnan@kitware.com">karthik.krishnan@kitware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A less obtrusive and more trivial change might be to add an overloaded constructor to the flood fill iterator that reads :<br><br> Iterator( imagePtr, fnPtr, seedList, exclusionImagePtr)<br> <br>This constructor would simply look exactly like the other constructor, except that it instead of calling InitializeIteration(), (which creates a new m_TemporaryPtr), it would set m_TemporaryPtr to exclustionImagePtr itself.<br>
<br>What do you think ?<br><br>Thanks<br><br></blockquote></div><br>Karthik,<br><br>I agree that is cleaner than my way, but it would still require editing all of the Filters that use the Iterator (<div>itkConnectedThresholdImageFilter, etc) to provide an option to let the user call the iterator's new constructor, right? <br>
<br>Let me know - if that is the best we can think of I'll code it up.<br>
<br clear="all">Thanks,<br><br>David</div><br>