id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
3466	OMEdit scrambles up package directory structure	Francesco Casella	Adeel Asghar	"Please consider the attached test package. It contains a directory named Test, which contains package.mo, package.order, A.mo and B.mo (two sub-packages). 

OMEdit opens it correctly. However, as soon as I modify something within package A (e.g., add a package constant definition), it does the following weird things:
- it creates two directories Test/A and Test/B
- it saves Test/A/package.mo and  Test/B/package.mo with the 
  content of the packages (including modifications)
- it keeps the old Test/A.mo and Test/B.mo files
- it complains that classes A and B are defined in multiple files

The intended behaviour should be
- if a package within Test is modified, the modifications should be
  applied to the existing files
- if a new package is added to Test (e.g. Test.C), the user should
  be given a choice between
  - adding it to package.mo 
  - adding it as C.mo
  - adding a directory Test/C and then a file package.mo there
"	defect	closed	critical	1.9.4	OMEdit		fixed