[Ves] vtkAxesActor

[Eduardo Poyart]

BTW, using vtkAxes, getting the geometry through vtkAxes::GetOutput
and setting it in a vesKiwiPolyDataRepresentation worked fine. I have
the axes nicely rendering. I added it as another child of my Transform
so that it's transformed with my model.

Eduardo


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