| Summary: | [ModelExplorer] Deleting an element that "contains" a diagram/table corrupts the model | ||
|---|---|---|---|
| Product: | [Modeling] Papyrus | Reporter: | Yann Tanguy <yann.tanguy> |
| Component: | Core | Assignee: | Vincent Lorenzo <vincent.lorenzo> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | cedric.dumoulin, cletavernier, mathieu.velten, scott.lee, toni.heimala, vincent.lorenzo |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | 403620 | ||
| Bug Blocks: | 360243 | ||
|
Description
Yann Tanguy
*** Bug 350254 has been marked as a duplicate of this bug. *** This bug has basically corrupted my whole UML project. How can I recover from it? Hi Tony, I tested on a very simple model. The corrupt file is the .di. I think you should have these things in this file : somewhere you should find <availablePage/> and in another place : <children/> These xml tags are empty, so, you should remove it in order to fix your model. Best regards, /Vincent Thanks Vincent! Removing <availablePage/> and <children/> from the .di file helped and I can view my model again! so as stated the PageRef is not removed from the sashWindow and the pageList when a diagram is deleted, but the pageIdentifier is set to null by tearDown*References in the DestroyElementCommand of the Diagram. I changed a bit the sash code to handle the case gracefully by just ignoring the diagram if the pageIdentifier is null but the underlying problem is still there. commited on branch and trunk. Hi, I'm writing a patch for this bug, but currently, I have an Undo/Redo problem, which seems be linked to the bug 348689. So we need to correct the bug 348689 before to provide a solution for this bug. ok nice, we also ran into the reparent bug and it will be a relief when fixed. anyway my "fix" can't hurt, and we can at least open "corrupted" files now. As the model corruption can be avoided, this task is not critical anymore. Changing the severity to normal. See Bug 401109, which tracks the current progress on this issue. I mark this one as a duplicate. *** This bug has been marked as a duplicate of bug 401109 *** *** Bug 324080 has been marked as a duplicate of this bug. *** |