id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
5786	OMEdit does not handle consecutive loading and unloading of mol files as expected.	Dietmar Winkler	Adeel Asghar	"When testing different versions of a mol file I got some error messages because OMEdit does not clean up its extraction location of a mol library after it was unloaded. 

This leads to problems. E.g., 
 1. Load older version of library A.mol
 2. Unload older version of library A.mol
 3. Load newer version of library A.mol where certain components were removed.

Now OMEdit will simply extract the newer A.mol on top of the temporary location where the older version was extracted before. Since the newer version does not contain some of the components (i.e., some .mo files less) when loading the newer A.mol OMEdit is now complaining about that some of the old classes are loaded but don't appear in the package.order. 
So you end up with a mixture of libraries which is highly confusing.

The easiest way to avoid this is that OMEdit simply cleans up after itself by deleting the extraction target of the mol library after it is unloaded."	defect	closed	high	1.16.0	OMEdit	v1.16.0-dev	fixed