Autodeletion should "dirty" diagram

[Paolo F Cantoni]

We've observed that if an object is deleted from an open diagram by virtue of an external action (such as deleting a package that contains the object).  Although the diagram is changed, EA does not mark the diagram as "dirty" (placing the * to the left of the name on the tab).

We think this should be changed.  That way, if you refactor the model and have a diagram that contains stuff that should be retained after the deletion, if it is set dirty afterwards, you know the refactoring wasn't correct.

Thoughts?  Votes?
Paolo

[size=0]©2006 Paolo Cantoni, -Semantica-[/size]

[sargasso]

Just a clarification query.

When you do that - and then close the 'affected' diagram  - does it ask whether to save it?  (NB this is different to marking it dirty!)

Also, is there any impact you have observed when that  diagram is reopened?

I ask because this may explain something I've been scratching my bald spot over.

bruce

20 Minute after EDIT: On second thought, no this isn't the same weirdity in behaviour or the same feature request.  But I may leave it here just to piggy back in the hope that someone has seen some inconsistency in having mutliple diagrams open and - after deleting an element from one,  it reappears as a "project browser" orphan - i.e it's not visible in any diagram, nor in the browser, but it sure as heell is there in the t_objects table???!!!///  

[Paolo F Cantoni]

Just a clarification query.

When you do that - and then close the 'affected' diagram  - does it ask whether to save it?  (NB this is different to marking it dirty!)

NO...

Also, is there any impact you have observed when that  diagram is reopened?

NO...

Paolo