For example, MU_AddPoint::size and MU_DeletePoint::size both includes sizeof(Model::Point) in their size totals.
Obviously it will be a PITA to try to correct this, so in the meantime it's safe to say the reported sizes are inaccurate.
I say this because I'm unsure what the purpose of this is. Obviously when an undo object owns the memory it should include its size, but probably not if the memory is represented in the model's size, but I don't know what the memory is meant to represent.
Obviously if you Add+Delete a point it doesn't make sense to report the size of two points objects.
EDITED: I think it's relate to Undo::undoRelease and Undo::redoRelease. It might make sense if Undo::size could tell if it was in the undo or redo stack to include the owned memory. I still don't know exactly; just reporting there's a relationship there.
For example, MU_AddPoint::size and MU_DeletePoint::size both includes sizeof(Model::Point) in their size totals.
Obviously it will be a PITA to try to correct this, so in the meantime it's safe to say the reported sizes are inaccurate.
I say this because I'm unsure what the purpose of this is. Obviously when an undo object owns the memory it should include its size, but probably not if the memory is represented in the model's size, but I don't know what the memory is meant to represent.
Obviously if you Add+Delete a point it doesn't make sense to report the size of two points objects.
EDITED: I think it's relate to
Undo::undoReleaseandUndo::redoRelease. It might make sense ifUndo::sizecould tell if it was in the undo or redo stack to include the owned memory. I still don't know exactly; just reporting there's a relationship there.