Bug 78192

Summary: Drag-n-drop uses associations incorrectly
Product: [Applications] umbrello Reporter: Zoltan Bartko <bartko.zoltan>
Component: generalAssignee: Umbrello Development Group <umbrello-devel>
Status: RESOLVED FIXED    
Severity: normal CC: lund
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Zoltan Bartko 2004-03-22 09:20:27 UTC 
Version:           current cvs (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 3.3.1 
OS:          Linux

If I drag and drop a class do a diagram that previously was not in the diagram, the associations that are dragged along with the class are not saved in the resulting file - upon opening the saved file these associations are not present. Further on, if a generalisation is dragged with the class and the class has no other associations, the direction of the generalisation is inverted. It does not happen if the class has some other association too. However, none of the dragged associations are saved in the final file. 

How to reproduce: create a diag with two classes that have a generalisation between each other and an association. Then delete the classes from the diag, drag them from the list box and watch what happens after saving and reloading. Then try the same with just the generalisation between the two classes.
Comment 1 Oliver Kellogg 2004-03-22 16:29:09 UTC 
Zoltan Barko wrote:
> If I drag and drop a class do a diagram that
> previously was not in the diagram, the associations
> that are dragged along with the class are not saved
> in the resulting file [...]

I cannot reproduce this.
I assume these actions are based on a previous C++
class import, is that correct?

> Further on, if a generalisation is dragged with the
> class and the class has no other associations, the
> direction of the generalisation is inverted.

Fixed in CVS, please verify.
Comment 2 Jonathan Riddell 2004-03-27 21:53:07 UTC 
Olivers commit seems to fix both problems.  Well done.
Comment 3 Jonathan Riddell 2004-03-28 20:50:55 UTC 
*** Bug 78633 has been marked as a duplicate of this bug. ***