[IGSTK-Users] Integration of ITK-Pipeline into IGSTK / Problem with igstkImageSpatialObject and igstkMeshSpatialObject

[Patrick Cheng]

Hi Stefan,

Sorry for the late reply. We are currently also working on a more 
universal VideoGrabber class, which had similar challenges in designing 
the refreshing cycle: The current IGSTK architecture doesn't handle 
dynamic scene well.

You have proposed some interesting idea here. Let me know if you have 
some new insights at this point and we can work together to meet those 
new requirements.

Patrick

On 8/30/2010 6:10 AM, Stefan wrote:
> em? Again, I probably have not enough experience with igstk to propose a
> perfect solution, but I think it should be possible to get the
> (non-const) pointer to the ITK data object through the event mechanism.
> The problem with this approach is that this might mess up the VTK
> representation classes. However, in my opinion this can be cured by
> updating the VTK classes every time the view is refreshed. As far as
> performance is concerned, this should not be a problem for most meshes
> and 2D images. It might be a big problem for 3D images. Maybe there
> could be two states for