After lots of superstitious bug hunting, I finally figured this out. The values I was passing to SetModelBounds() had ymin = 3.5 and ymax = 0.16. The result was that the surface looked correct and the proper range was being shown, but for some reason this affects the way the surface gets rendered.... wow.... that took almost 2 days to figure out.<div>
<br></div><div>Any idea why this would happen? Could/should vtkSampleFunction reorder the bounds if the SetModelBounds() is called with xmin>xmax, ymin>ymax, or zmin>zmax?</div><div><br></div><div>Just to be clear, this issue had nothing to do with QVTKWidget whatsoever.<br>
<div><div><br></div><div>~Luke<br><br><div class="gmail_quote">On Mon, Jul 2, 2012 at 12:25 PM, Bill Lorensen <span dir="ltr"><<a href="mailto:bill.lorensen@gmail.com" target="_blank">bill.lorensen@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">No idea.<div class="im HOEnZb"><br><br><div class="gmail_quote">On Mon, Jul 2, 2012 at 3:22 PM, Dale "Luke" Peterson <span dir="ltr"><<a href="mailto:hazelnusse@gmail.com" target="_blank">hazelnusse@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Attached is what it looks like outside of QVTKWidget.<br>
</blockquote></div><br><br clear="all"><br></div><div class="HOEnZb"><div class="h5">-- <br>Unpaid intern in BillsBasement at noware dot com<br><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>“People call me a perfectionist, but I'm not. I'm a rightist. I do something until it's right, and then I move on to the next thing.” <br>
― James Cameron<br>
</div></div></div>