2009/5/30 Andreas Rueckert <[email protected]>: said > But some users might be confused and want to delete such a class?
I know that a user has had a problem with this in the past. Designing a whole diagram, then spotting some class that he didn't understand the purposes of, deleting it and then the whole of his work also being deleted as a result of the cascaded delete. We maybe need some level of warning when a deletion will have a heavy knock on effect. Maybe we need some method on the model subsystem that will return a list of elements that will be deleted as a side effect of a delete request without actually doing the delete itself. We could then prompt a warning to the user of what would be deleted before doing the actual deletion itself. Bob. ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2357152 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
