That's great! I'm curious, do the generated axes have colors?<br><br>Pat<br><br><div class="gmail_quote">On Wed, Mar 13, 2013 at 3:36 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">BTW, using vtkAxes, getting the geometry through vtkAxes::GetOutput<br>
and setting it in a vesKiwiPolyDataRepresentation worked fine. I have<br>
the axes nicely rendering. I added it as another child of my Transform<br>
so that it's transformed with my model.<br>
<span class="HOEnZb"><font color="#888888"><br>
Eduardo<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On Tue, Mar 12, 2013 at 10:31 PM, Eduardo Poyart <<a href="mailto:poyart@gmail.com">poyart@gmail.com</a>> wrote:<br>
> I'll wait for the Kitware github project then.<br>
><br>
> Eduardo<br>
><br>
> On Tue, Mar 12, 2013 at 9:28 PM, Aashish Chaudhary<br>
> <<a href="mailto:aashish.chaudhary@kitware.com">aashish.chaudhary@kitware.com</a>> wrote:<br>
>> On Wed, Mar 13, 2013 at 12:07 AM, Eduardo Poyart <<a href="mailto:poyart@gmail.com">poyart@gmail.com</a>> wrote:<br>
>>> I can share something soon, not all of my source but the parts that do<br>
>>> this change. I'm interested in doing that. I think I can fork<br>
>>> Aashish's project on github and put my changes there. Is it kept up to<br>
>>> date?<br>
>><br>
>> It is. But I am in the process of making VES as part of Kitware repo<br>
>> (<a href="https://github.com/Kitware" target="_blank">https://github.com/Kitware</a>). Should be done this week.<br>
>> Then we can use merge request to include contributions from folks<br>
>> outside kitware.<br>
>><br>
>>><br>
>>> However, it's not very general at this point, I have to clean it up.<br>
>><br>
>> Sure.<br>
>><br>
>>> What I did was: copied the vesKiwiImageWidgetRepresentation to my own<br>
>>> ImageWidgetRepresentation, and I handle single touch, two touch, etc<br>
>>> instead of sending the events up the chain. I'm currently not using<br>
>>> the CameraSpinner because it's too tied to the camera. It would be<br>
>>> interesting if it operated on a Transform instead (both the Spinner<br>
>>> and the CameraInteractor).<br>
>>><br>
>>> I store the model's Transform in this class and I add it to the scene<br>
>>> graph above the actor. For the slice picking, I just transform the ray<br>
>>> by the inverse model transform before doing the intersection tests.<br>
>><br>
>> Nice.<br>
>><br>
>>><br>
>>> I don't remember exactly why I had to copy<br>
>>> vesKiwiImageWidgetRepresentation instead of subclassing it. In general<br>
>>> I found it hard to subclass Kiwi classes, mostly due to needed things<br>
>>> being inside Internal, without accessors.<br>
>><br>
>> We have a branch that we will merge hopefully soon that will fix this.<br>
>><br>
>>><br>
>>> Eduardo<br>
>>><br>
>>><br>
>>> On Tue, Mar 12, 2013 at 8:04 PM, Pat Marion <<a href="mailto:pat.marion@kitware.com">pat.marion@kitware.com</a>> wrote:<br>
>>>> Yeah, I guess I should add that the concept exists in the<br>
>>>> vesKiwiPlaneWidget, which is used as the clipping plane in the brain atlas<br>
>>>> demo, but it's hasn't been generalized so that you can enable interaction<br>
>>>> for any model.<br>
>>>><br>
>>>> Pat<br>
>>>><br>
>>>><br>
>>>> On Wed, Mar 13, 2013 at 1:00 PM, Aashish Chaudhary<br>
>>>> <<a href="mailto:aashish.chaudhary@kitware.com">aashish.chaudhary@kitware.com</a>> wrote:<br>
>>>>><br>
>>>>> On Tue, Mar 12, 2013 at 10:51 PM, Pat Marion <<a href="mailto:pat.marion@kitware.com">pat.marion@kitware.com</a>><br>
>>>>> wrote:<br>
>>>>> > Very cool, so I guess you re-routed the touch gestures from the camera<br>
>>>>> > to<br>
>>>>> > individual models? Did you use the vesKiwiWidgetRepresentation<br>
>>>>> > interface?<br>
>>>>> > How about the picking code, did you use the cell picker or something<br>
>>>>> > else?<br>
>>>>> > Not sure if you are able to share your source, but I'm sure there would<br>
>>>>> > be<br>
>>>>> > interest in the community to see example code for rotating individual<br>
>>>>> > models, because that's not something we've shown in KiwiViewer before.<br>
>>>>><br>
>>>>> +1 would be nice to have this feature shown / exists.<br>
>>>>><br>
>>>>> ><br>
>>>>> > Pat<br>
>>>>> ><br>
>>>>> ><br>
>>>>> > On Wed, Mar 13, 2013 at 12:41 PM, Eduardo Poyart <<a href="mailto:poyart@gmail.com">poyart@gmail.com</a>><br>
>>>>> > wrote:<br>
>>>>> >><br>
>>>>> >> Thanks! I'll try with the vtkAxisSource. I changed my system to keep<br>
>>>>> >> the camera fixed and rotate the models (since I need multiple models<br>
>>>>> >> rotating independently). So the model transforms are under my control.<br>
>>>>> >><br>
>>>>> >> Eduardo<br>
>>>>> >><br>
>>>>> >><br>
>>>>> >> On Tue, Mar 12, 2013 at 7:37 PM, Pat Marion <<a href="mailto:pat.marion@kitware.com">pat.marion@kitware.com</a>><br>
>>>>> >> wrote:<br>
>>>>> >> > Hi,<br>
>>>>> >> ><br>
>>>>> >> > That's correct, the vtkAxisActor is not supported. Only the<br>
>>>>> >> > vtkRenderingCore module is built, the rest of VTK's OpenGL rendering<br>
>>>>> >> > does<br>
>>>>> >> > not support OpenGL ES 2.0.<br>
>>>>> >> ><br>
>>>>> >> > You can use the vtkAxisSource to generate geometry for a set of axes,<br>
>>>>> >> > and<br>
>>>>> >> > you can render them using VES actors. VES has support for actor<br>
>>>>> >> > overlays, if<br>
>>>>> >> > you are trying to acheive a corner annotation. But, there is not<br>
>>>>> >> > currently<br>
>>>>> >> > an example demonstrating how to link a VES actor transform to the<br>
>>>>> >> > camera<br>
>>>>> >> > orientation.<br>
>>>>> >> ><br>
>>>>> >> > Pat<br>
>>>>> >> ><br>
>>>>> >> > On Wed, Mar 13, 2013 at 12:32 PM, Eduardo Poyart <<a href="mailto:poyart@gmail.com">poyart@gmail.com</a>><br>
>>>>> >> > wrote:<br>
>>>>> >> >><br>
>>>>> >> >> Hi,<br>
>>>>> >> >><br>
>>>>> >> >> I'm trying to use vtkAxesActor, but vtkAxesActor.h includes<br>
>>>>> >> >> vtkRenderingAnnotationModule.h which doesn't exist in the vtk<br>
>>>>> >> >> implementation in ves. Are RenderingAnnotations (therefore<br>
>>>>> >> >> AxesActors)<br>
>>>>> >> >> not supported?<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>
>>>>> > _______________________________________________<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>
>>>>> | Aashish Chaudhary<br>
>>>>> | R&D Engineer<br>
>>>>> | Kitware Inc.<br>
>>>>> | <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>>>><br>
>>>><br>
>><br>
>><br>
>><br>
>> --<br>
>> | Aashish Chaudhary<br>
>> | R&D Engineer<br>
>> | Kitware Inc.<br>
>> | <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
</div></div></blockquote></div><br>