Lee Newberg

Sounds good. Forgive my ignorance about the implementation of `vtkSmartPointer` ... with some implementations of smart pointers, one has to be careful about passing from one smart pointer to another...

I agree: use `vtkSmartPointer` to declare the private members, use ordinary C++ pointers for the constructor arguments, mimic the usage in PR #8148.

Would it work to not supply the `scene` as a constructor argument, instead asking for `node->GetScene()` either at the time of `vtkMRMLRemoveNodeFromScene` construction (to be stashed in `this->Scene`) or at...

Would it make sense to add a new method, `vtkMRMLNode::SetAutomaticRemoveNodeFromScene(bool)` (or similar, with corresponding `Get` if appropriate) to ask the node to call `this->GetScene()->RemoveNode(this)` within its own destructor? (Or is...

With the changes we've made in the interim, I'd like to reconsider the possibility of a template. That way instead of having two variables in play: ```cpp vtkMRMLMarkupsCurveNode* resampledCurveNode =...

I am working on this, with guidance from @sjh26.