[vtkusers] Single proxy class for a vector of vtkUnstructuredGrids

[Andrew Parker]

Hi,

So that was exactly where I wanted to go, until I found that it was not a
true proxy, which is fine it wasn't intended to be, but instead copies
everything.  So I have had to delete components to save them being in
memory twice.  It is a shame this class cannot behave as is, except only in
a "shallow" fashion and not copy the data.  Indeed it would be also useful
if it maintained a reference to the original data such that if I called
Transform/modified one of the components then the original component would
be modified too.

Is any of that possible, in particular the lightweight version in terms of
memory?

Cheers,
Andy

On 11 June 2012 13:48, Bill Lorensen <bill.lorensen at gmail.com> wrote:

> Take a look at vtkAppendFilter.
>
> On Mon, Jun 11, 2012 at 4:37 AM, Andrew Parker
> <andy.john.parker at googlemail.com> wrote:
> > Hi,
> >
> > I have several vtkUnstructuredGrid(s) that I read in from disk, they are
> > separate components of a large model.  For various reasons I'd like to be
> > able to keep them separate but, for the majority of my program proxy them
> > all by one interface as one single "glued" object of that type, in this
> case
> > a single vtkUnstructuredGrid.  For example, if I have a file that I read
> in
> > for a nut, and a second file for a bolt, I would like them to remain
> > separate, but pass around an object that allowed me to do, say
> GetPoints(),
> > on a single vtkUnstructuredGrid object that gave me all the points in
> both
> > the nut and bolt meshes.  Actually, I would like to in a sense have the
> > whole interface for vtkUnstructuredGrid and anything beneath it, but
> behind
> > hold a vector of vtkUnstructuredGrids, or indeed another type,
> vtkpolydata
> > for example.
> >
> > Is this possible?  I do not think the vtkMultiBlock... is what I want.
> >  Alternatively, if this is not possible, is there anything that will
> allow
> > me to "add" using operator+ for example the nut and bolt together to get
> a
> > single mesh back.  This is not really what I want but would suffice.
> >
> > I would much prefer the former, but the latter is fine if the former is
> not
> > possible.
> >
> > Any help much appreciated.  Again, primary importance is one interface
> that
> > under the hood is a vector of said types, where that type need not be a
> > vtkunstructuredGrid, but that would be ideal initially....
> >
> > Cheers again,
> > Andy
> >
> > _______________________________________________
> > Powered by www.kitware.com
> >
> > Visit other Kitware open-source projects at
> > http://www.kitware.com/opensource/opensource.html
> >
> > Please keep messages on-topic and check the VTK FAQ at:
> > http://www.vtk.org/Wiki/VTK_FAQ
> >
> > Follow this link to subscribe/unsubscribe:
> > http://www.vtk.org/mailman/listinfo/vtkusers
> >
>
>
>
> --
> Unpaid intern in BillsBasement at noware dot com
>



-- 

__________________________________

   Dr Andrew Parker

   Em at il:  andrew.parker at cantab.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.vtk.org/pipermail/vtkusers/attachments/20120611/480bb275/attachment.htm>