VTK Slice Disappear After Some User Interaction #540
-
Hi! I am having a similar issue with my volumes disappearing as @maflancer in discussion post #539. However, I have not yet deployed my application though, so that isn't part of my issue. When I am using files with fewer blocks I can interact with the slices for longer (changing slice index or plane), whereas files with more blocks only permit a few interactions. This may be because my approach to re-rendering the slice actors is inefficient, but the memory consumption of my application appears to be constant according to Windows Task Manager. This is what my output looks like when functioning properly: Here is the function that handles the change in slice plane which then triggers a few more functions to change the VOI:
Then the two key functions for actually changing the VOI are:
Finally, the following is my GUI for the slices card:
For reference, most of my code is based off of the example application in the trame tutorial except my data is a mutli-block dataset. EDIT: I am using |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
So for VtkLocalView and the Local part of the VtkRemoteLocalView might get confused with the Add/RemoveActor. Try to play with visibility of the actor instead. Otherwise, if you use the RemoteView it will just work. |
Beta Was this translation helpful? Give feedback.
So for VtkLocalView and the Local part of the VtkRemoteLocalView might get confused with the Add/RemoveActor. Try to play with visibility of the actor instead. Otherwise, if you use the RemoteView it will just work.