[Uml-devel] How to do cut-n-paste operations?

[Brian Thomas]

	Ok I've just sent in a number of fixes which, alongside Oliver's latest changes,
	should make the code base a bit more stable. Comments on the changes 
	more or less describe this, so I wont re-interate them here.

	But I did see that there appears to be a conflict in methodology in when
	an object should be deleted from the project. One obvious problem is
	that the associationwidget doesnt appear to be able to cause its child
	UMLAssociation to exit when it does. (this formerly done in its cleanup
	method). IF cleanup() deletes the child, then cut-n-paste operations with
	associations have a problem. Where then IS the association deleted? I
	have a feeling that this may be a source of a memory leak.

	My feeling is that the child associations XMI representation should be 
	copied *before* the  parent associationwidget is deleted. Then the 
	parent (and child) can be safely deleted. The XMI representation can then
	 be used to paste new associations. I didnt look at the code that handles
	cut n paste, but I dont believe its currently done this way. Comments?

	I also see that the 'undo' operation is still a bit buggy. Sometimes when
	I cut a number of things, and then 'undo' I get a crash upon exiting the
	program.

				-b.t.