You're reading it wrong. The model must signal to its users when it's about to start changing its "geometry". So, no matter what is removing the rows from the model, it must tell the outside world that it happened. The sequence of events when a view removes rows from the model is such:
The view calls
model->removeRows()
.The model calls
beginRemoveRows()
The model actually removes the rows from the internal data.
The model calls
endRemoveRows()
.
If you implement some other interface that will remove the rows without calling model->removeRows()
, you have to do exactly the same thing. It doesn't matter if it's a view or some other code that removes rows from the model, the model's behavior must be the same or else nothing will work.
You can architect an adapter class that's inserted between your SceneGraph and the Model. It should hold a pointer to the scenegraph and the model, and translate the operations between the two.