You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm experiencing an issue where calling view_update() for VtkRemoteView does not always work. It seems like the call might be throttled?
It results in a clunky user interface in this slicing example. After moving the plane widget in the scene on the left, the scene on the right should immediately update. However it does not always update, sometimes requireing a user-click in either of the two views for the one on the right to update
So it is a timing issue. Both views end up in animation, which makes the view.update() a NoOp. But then the animation get canceled before the encoding queue get fully flushed/consumed.
Can you make the callback happen when you actually drag the widget?
Hm. Using interaction_event='always' (vtk.vtkCommand.InteractionEvent) in PyVista's add_plane_widget() fixes it for this case. However we don't always want to use this as slicing large data sets in this fashion would have serious performance implications.
I'm experiencing an issue where calling
view_update()
forVtkRemoteView
does not always work. It seems like the call might be throttled?It results in a clunky user interface in this slicing example. After moving the plane widget in the scene on the left, the scene on the right should immediately update. However it does not always update, sometimes requireing a user-click in either of the two views for the one on the right to update
view-update.mov
The text was updated successfully, but these errors were encountered: