[IGSTK-Users] PointData and CellData accessible in MeshObject ?

[Michel Audette]

Hi Vincent,

I believe that the intention was to have ITK programs do the processing that
produce points, cells, and meshes, and deal with const point sets so as to
limit the number of possible states in the IGSTK state machine.

We will enter your feature request in the bug tracker, and look into it
further. By all means, if you feel that a locally modified version of
igstkMesh fulfills your requirements, give it a try.

Best wishes,

Michel

On Fri, Jul 3, 2009 at 5:16 AM, Vincent Gratsac <vincent.gratsac at irisa.fr>wrote:

> Hi all,
>
> I want to store PointData in a MeshObject as it is possible to do with the
> corresponding itk object itk::Mesh.
> Unfortunately, it is not possible to inherit the MeshObject class because
> the internal itk::Mesh object is store as a private member.
> So currently, it seems that the only way to do this is to locally modify
> the igstkMeshObject file in order to make accessible PointData (and
> CellData) of the internal itk::Mesh object from the igstk::MeshObject class.
>
> Does anyone know another way to do it ? If the answer is no, do you plan to
> make this parameters accessible from the igstk::MeshObject class ?
>
> Thank you,
>
> Vincent
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-users
>



-- 
Michel Audette, Ph.D.
R & D Engineer,
Kitware Inc.,
Chapel Hill, N.C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/igstk-users/attachments/20090710/f206186d/attachment-0001.html>