A little later than I said, but I just pushed these changes. Thanks for reporting this issue.<div><br></div><div>Marcus<br><br><div class="gmail_quote">On Tue, May 25, 2010 at 10:21 AM, Eric E. Monson <span dir="ltr"><<a href="mailto:emonson@cs.duke.edu">emonson@cs.duke.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word">Do you want me to add it to the bug tracker in case you can't get to it right away?<div>
<br></div><div>Thanks,</div><div>-Eric</div><div><div></div><div class="h5"><div><br><div><div>On May 25, 2010, at 9:56 AM, Marcus D. Hanwell wrote:</div><br><blockquote type="cite"><div class="gmail_quote">On Mon, May 24, 2010 at 10:49 AM, Eric E. Monson <span dir="ltr"><<a href="mailto:emonson@cs.duke.edu" target="_blank">emonson@cs.duke.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Hey Marcus,<div><br></div><div>Thanks -- that clarifies things a bit. </div><div><br></div><div>So, it looks like each ContextItem has access to it's own scene, and so it's up to us to make sure when we implement any new context item to make sure to set the scene to Dirty after we make any changes?</div>
<div><br></div><div>Maybe something like this patch should be applied to vtkBlockItem?:</div><div><br></div></div></blockquote><div>That is a great suggestion, I will update this class. I should also add a few tests with mouse interaction to improve the coverage. Great to have someone testing out the code and pointing out a few of the neglected classes.</div>
<div><br></div><div>Thanks,</div><div><br></div><div>Marcus</div></div>
</blockquote></div><br></div></div></div></div></blockquote></div><br></div>