#include <vtkSMMultiDisplayProxy.h>
Inheritance diagram for vtkSMMultiDisplayProxy:
Public Member Functions | |
vtkTypeRevisionMacro (vtkSMMultiDisplayProxy, vtkSMCompositeDisplayProxy) | |
void | PrintSelf (ostream &os, vtkIndent indent) |
virtual void | SetLODCollectionDecision (int) |
void | Update () |
Static Public Member Functions | |
vtkSMMultiDisplayProxy * | New () |
Protected Member Functions | |
vtkSMMultiDisplayProxy () | |
~vtkSMMultiDisplayProxy () | |
virtual void | CreateVTKObjects (int num) |
This class has an unfortunate name ... It always collects and displays the LOD on node zero (client when we enable client server). TODO: I wonder if we can get rid of this class altogether! It doesn't really do much.
Definition at line 29 of file vtkSMMultiDisplayProxy.h.
|
|
|
|
|
Reimplemented from vtkSMCompositeDisplayProxy. Reimplemented in vtkSMIceTMultiDisplayProxy. |
|
|
|
Reimplemented from vtkSMCompositeDisplayProxy. Reimplemented in vtkSMIceTMultiDisplayProxy. |
|
Overridden to set LOD collection decision to always Collect. Reimplemented from vtkSMCompositeDisplayProxy. Reimplemented in vtkSMIceTMultiDisplayProxy. |
|
Update like normal, but make sure the LOD is collected. I encountered a bug. First render was missing the LOD on the client. Reimplemented from vtkSMCompositeDisplayProxy. |
|
Given the number of objects (numObjects), class name (VTKClassName) and server ids ( this->GetServerIDs()), this methods instantiates the objects on the server(s) Reimplemented from vtkSMCompositeDisplayProxy. Reimplemented in vtkSMIceTMultiDisplayProxy. |