When a model element is deleted in the model tree, the editor tab for that element stays open. If the tab is then saved, the element is written back into the model and reappears in the tree.
Is this intended behaviour, or a bug? Right now it can act as an accidental undo for a deletion, but it can equally resurrect an element the user genuinely wanted gone - and the tab itself refers to something that no longer exists.
My feeling is that closing (discarding) the tab automatically on deletion would be clearly better and less surprising, but I may be missing a use case where the current behaviour is deliberate.
Would this be worth changing, or is there a reason it’s set up this way?
It"s a bug and the reason for many troubles. Please fix it. It might be even reported before. But sometimes the editor tab is closed within deletion. Can’t tell when. So it doesn’t replicate 100%.
@urbanekv So, sometimes it closes when you delete some object, and sometimes it doesn’t? Maybe the Architect used to handle tabs that way, but then an update came out and it started handling removal differently?
In the early architect days it didn’t close the documents at all. We are using version 2025.10 of Architect, desktop version. At that version it normally closes the document when it’s deleted from the tree. However, sometimes it just don’t work well and the tab is not closed. I can’t replicate it. Nevertheless, no doubts, the intended behavior is to close the document when it’s deleted from the tree.