what class are you talking when you say "SetPosition method"?

sorry, vtkMRMLCameraNode

The fundamental issue here is that a vtkCamera does not know what vtkRenderer is drawing it, and so it cannot know the bounding box of the props in the scene. Therefore, any classes which can adjust the camera, such as vtkMRMLCameraNode but which do not have access to a renderer cannot predict whether they will cause clipping issues when they move the camera, and cannot preemptively fix those clipping issues.

So, either vtkCamera must gain a reference to vtkRenderer (untenable) or everyone who moves a vtkCamera must also have a reference to the associated vtkRenderer and remember to call vtkRenderer::ResetClippingRange (untenable)

Or, we could just set the far clipping distance to be the max(10000, 2*vtkCamera->GetDistance) which is a hack but would make the problems go away as long as our patients are less that 10 meters tall

Nice investigative work.

Other possible alternative:

1. Update vtkMRMLCameraNode::ResetClippingRange to invoke event like "vtkMRMLCameraNode::ResetClippingRangeFlag"

2. Update vtkSlicerCamerasModuleLogic::ProcessMRMLSceneEvents so that it observe camera node

3. The camera logic would retrieve the render associated with the view where the camera is and call the method on the renderer

Assumption: A camera node can be associated with only one view.