[umbrello] [Bug 425281] Double association in the diagram after renaming a foreign key constraint

[Robert Hairgrove]

https://bugs.kde.org/show_bug.cgi?id=425281

Robert Hairgrove <code at roberthairgrove.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |code at roberthairgrove.com

--- Comment #1 from Robert Hairgrove <code at roberthairgrove.com> ---
I'm not sure that this bug is not present in other views, too.

If you draw an association between an actor and a use case, then delete it and
save the file, there is still an element in the XMI file with tag
"UML:Association" and the corresponding "UML:AssociationEnd" elements. The only
thing that gets deleted is the <assocwidget> tag under the <diagram>.

If another association is created, then another UML:Association as well as the
new <assocwidget> is created; the old UML:Association remains apparently as a
zombie.

Renaming the association appears to work correctly, however.

-- 
You are receiving this mail because:
You are the assignee for the bug.