GoView.RescaleToFit depends on the result of GoView.ComputeDocumentBounds, which by default just calls GoDocument.ComputeBounds.
Sorry, I forgot to write the version. It’s 2.5.1, so that doesn’t seem to be the problem.
You haven’t overridden any of the methods I mentioned?
No, I havent’t.
Because you say it’s only a problem when you change your collection of nodes to occupy a smaller area, I’m wondering if there are some Visible but not seen objects remaining at the further location(s). Do you use some kind of background object?
There was a misunderstanding. At the beginning I don’t use the RescaleToFit, so it’s all my sizing and positioning. So the space is fully used.