Hi Jean,<br><br>I did read the question, but I was hoping someone else would have some time to look into it. It definitely is a bug that needs to be fixed. I have not yet tried to reproduce it and start looking into it. My hunch is that the extent translator is being overridden or is not being propagated throughout the pipeline somehow.<br>
<br>Please file a bug report (assign it to me, Berk or Utkarsh) and we will try to get it fixed for 3.6.2.<br><br clear="all">David E DeMarle<br>Kitware, Inc.<br>R&D Engineer<br>28 Corporate Drive<br>Clifton Park, NY 12065-8662<br>
Phone: 518-371-3971 x109<br>
<br><br><div class="gmail_quote">On Fri, Sep 25, 2009 at 9:27 AM, Jean M. Favre <span dir="ltr"><<a href="mailto:jfavre@cscs.ch">jfavre@cscs.ch</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;">
David<br>
<br>
I have seen the new files checked in yesterday to add the concept of<br>
Resolution to the pipeline. Sounds very neat. You must be the Extent<br>
Translator expert. Am I right? :-)<br>
<br>
do you have an explanation for my request of 2 weeks ago (nobody<br>
answered and I have made no progress)<br>
<br>
<a href="http://www.paraview.org/pipermail/paraview/2009-September/013608.html" target="_blank">http://www.paraview.org/pipermail/paraview/2009-September/013608.html</a><br>
<font color="#888888"><br>
Jean<br>
</font></blockquote></div><br>