Hi Eduardo<br><br><div class="gmail_quote">On Mon, Mar 18, 2013 at 5:37 PM, Eduardo Poyart <span dir="ltr"><<a href="mailto:poyart@gmail.com" target="_blank">poyart@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Pat,<br>
<br>
Thanks, it has been really helpful. It turns out I can't use<br>
vesKiwiPlaneWidget, because it doesn't have an actor() accessor like<br>
vesKiwiPolyDataRepresentation does. In my scene graph, I have a<br>
Transform node with my model underneath, and I want the plane node to<br>
be another child of the same Transform so that it moves with it.<br>
<br>
I guess my suggestion would be to add actor() accessors to all<br>
Representations to make them consistent. I think it's a common need to<br>
create your own scene graph with the provided widgets.<br></blockquote><div><br></div><div>This sounds like a good idea. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
This would introduce an interesting issue: for representations that<br>
have multiple sub-representations (like vesKiwiPlaneWidget itself),<br>
the sub-representations should be in their own scene graph, i.e. child<br>
of a Transform. It would actually be cleaner to modify changes to the<br>
parent Transform instead of individually modifying all the Transforms<br>
(for example in vesKiwiPlaneWidget::onTransformModified()).<br>
<br>
You can also think about making the Representations implement the<br>
vesNode interface so that they can be directly added to the scene<br>
graph.<br></blockquote><div><br></div><div>This is an interesting suggestion but I think if we do this then it may change the API (implementation more so) of representations somewhat although it does have some benefits too. </div>
<div>When we get an opportunity we will discuss this possibility.</div><div><br></div><div>Thanks, </div><div><br></div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Best<br>
<span class="HOEnZb"><font color="#888888">Eduardo<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On Mon, Mar 18, 2013 at 1:14 AM, Pat Marion <<a href="mailto:pat.marion@kitware.com">pat.marion@kitware.com</a>> wrote:<br>
> Ok. I think you'll find the vesKiwiPlaneWidget is missing a crucial<br>
> function- a function to initialize the plane position, orientation, and<br>
> scale. I just merged a branch into next, called plane-widget-api which adds<br>
> some more helpful methods. It's still not great, and is missing<br>
> documentation, I want to improve it later when I have some time. But, you<br>
> can now access the vtkTransform and call the vtkTransform api to position<br>
> and rotate and scale the widget. If you use it and have suggestions for<br>
> possible improvements, let me know!<br>
><br>
> Pat<br>
><br>
><br>
> On Mon, Mar 18, 2013 at 5:58 PM, Eduardo Poyart <<a href="mailto:poyart@gmail.com">poyart@gmail.com</a>> wrote:<br>
>><br>
>> Thank you for the pointers. I see that it's wrapped by the<br>
>> vesKiwiPlaneWidget, I'll try that route.<br>
>><br>
>> Cheers<br>
>> Eduardo<br>
>><br>
>> On Sun, Mar 17, 2013 at 9:29 PM, Pat Marion <<a href="mailto:pat.marion@kitware.com">pat.marion@kitware.com</a>><br>
>> wrote:<br>
>> > Have you seen the interactive brain atlas demo in KiwiViewer? That uses<br>
>> > a<br>
>> > clipping plane. Is that similar to what you are trying to do? The<br>
>> > plane is<br>
>> > generated using the vtkPlaneSource, then set the color and transparency<br>
>> > using vesKiwiPolyDataRepresentation::setColor().<br>
>> ><br>
>> > Pat<br>
>> ><br>
>> > On Mon, Mar 18, 2013 at 2:18 PM, Eduardo Poyart <<a href="mailto:poyart@gmail.com">poyart@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> Hi,<br>
>> >><br>
>> >> I would like to add a transparent plane to the scene graph. I need to<br>
>> >> indicate a cutting plane for simulation of an ultrasound procedure.<br>
>> >> Ideally it would be a transparent green quad, with no texture.<br>
>> >><br>
>> >> What would be the best way to do it?<br>
>> >><br>
>> >> Thanks<br>
>> >> Eduardo<br>
>> >> _______________________________________________<br>
>> >> Ves mailing list<br>
>> >> <a href="mailto:Ves@public.kitware.com">Ves@public.kitware.com</a><br>
>> >> <a href="http://public.kitware.com/cgi-bin/mailman/listinfo/ves" target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/ves</a><br>
>> ><br>
>> ><br>
><br>
><br>
_______________________________________________<br>
Ves mailing list<br>
<a href="mailto:Ves@public.kitware.com">Ves@public.kitware.com</a><br>
<a href="http://public.kitware.com/cgi-bin/mailman/listinfo/ves" target="_blank">http://public.kitware.com/cgi-bin/mailman/listinfo/ves</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>| Aashish Chaudhary <br>| R&D Engineer <br>| Kitware Inc. <br>| <a href="http://www.kitware.com">www.kitware.com</a>