Thanks! Yes I will send a PR. Another thing. The oblique reslicing is extremely slow for real time applications; I have noticed that the 2D image mapper is not using the newer vtkImageResliceMapper. Do you have plans to rewrite the mappers using the “new” VTK mappers and actors for image slices?
Best regards, Federico El El mié, 15 abr 2020 a las 18:27, Dinkelacker, Stefan < s.dinkelac...@dkfz-heidelberg.de> escribió: > Hi, > > > should be fine. When it was implemented there was only a single 3d window > and so I guess it never appeared to be a problem to not have a local > storage there. :-) Do you contribute? > > > Best, > > Stefan > ------------------------------ > *Von:* Federico Milano <fmil...@gmail.com> > *Gesendet:* Mittwoch, 15. April 2020 16:30 > *An:* mitk-users@lists.sourceforge.net > *Betreff:* Re: [mitk-users] No LocalStorage for > PlaneGeometryDataVtkMapper3D > > I have added a local storage for the per renderer resources to > PlaneGeometryDataVtkMapper3D and it is working now, I just wanted to know > if you see any drawback in this case. > > Thanks! > > Fede > > On Wed, Apr 15, 2020 at 4:07 PM Federico Milano <fmil...@gmail.com> wrote: > >> Hi. I'm trying to show an image slice in more than one 3D view, and I'm >> getting OpenGL errors. It seems that the same vtkProp is being used for >> both vtkRenderers. I have noticed that PlaneGeometryDataVtkMapper3D does >> not use a LocaStorage, is there any reason for that? >> >> Thanks! >> >> Federico >> >
_______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
