Summary: | Delete attributes or operations in classes | ||
---|---|---|---|
Product: | [Applications] umbrello | Reporter: | abel123 |
Component: | general | Assignee: | Umbrello Development Group <umbrello-devel> |
Status: | RESOLVED FIXED | ||
Severity: | major | CC: | ralf.habacker |
Priority: | NOR | ||
Version: | 2.20.1 (KDE Applications 16.08.1) | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | All | ||
Latest Commit: | http://commits.kde.org/umbrello/a86130613067940d27c98f6f845037817c705297 | Version Fixed In: | 2.20.80 (KDE Applications 16.11.80) |
Description
abel123
2016-11-17 10:59:10 UTC
To reproduce this behaviour try creating a class/interface with several (5 or 6) attributes/operations and then copy it and duplicate it. Then change the duplicated or copied class by deleting attributes or operations. This issue is caused by a bug in the duplicate function. On ListPopupMenu::mt_Clone event a new cloned UMLObject is created and the UMLObject dock window in umbrello build from git master shows that new attributes are created but are still assigned to the old class. The related location where it fails is shown below: /** * Make a clone of the UMLAttribute. */ UMLObject* UMLAttribute::clone() const { //FIXME: The new attribute should be slaved to the NEW parent not the old. UMLAttribute *clone = new UMLAttribute(umlParent()); copyInto(clone); return clone; } Git commit a86130613067940d27c98f6f845037817c705297 by Ralf Habacker. Committed on 17/11/2016 at 23:41. Pushed by habacker into branch 'Applications/16.12'. Fix 'Delete attributes or operations in classes'. FIXED-IN:2.20.80 (KDE Applications 16.11.80) M +4 -0 umbrello/umlmodel/classifier.cpp http://commits.kde.org/umbrello/a86130613067940d27c98f6f845037817c705297 |