It has to be this way, or the WND file would not be constructed properly. The problem is that until now people have toyed with WND files like they would an INI file without understanding exactly how they work.
The hierarchy structure is critical to the functionality of the window - and the order in which window objects appear in the WND file (when you open it in WordPad) reflects the hierarchy. In addition, parents and children have to be related properly (LOL) and thus appear in the correct place in the file - the WND file is almost like a 'pecking order' of all the windows in it.
Youll see that the higher an object is in the hierarchy, the lower it is in the WND file. Higher objects take preference over lower objects, since the WND file is made up in 'layers'. It wasnt used, but you can move objects between layers on the fly with BELOW or ABOVE on the STATUS field.
If you want to edit or change a window object that overlaps with another, move it using the heirarchy view first (you can drag and drop itmes in the hierarchy menu to get them at the top), edit it, and then move it back to where you want it.
It sounds complicated, but if you think in terms of 'keeping everything within the framework of the hierarchy' rather than 'where it is and what it looks like' first, you cant go far wrong
Editing Utils Available
