Incorrect order of folders in MapDefinition

[gBecker]

Suppose you have the following structure in MapDefinition:

FolderA
|_ Folder1
|_ Folder2

then the plain order of the layergroups in xml is:

Folder_A
Folder_1
Folder_2

Now push the button to move up Folder_2 to be the top child of Folder_A and lets say you pushed it accidentally one time to much. The resulting display seems to be correct

FolderA
|_ Folder2
|_ Folder1

but in xml the order is now

Folder_2
Folder_A
Folder_1

I think this is not correct even though the xml is valid related to its scheme.

As a sidenote: I've got some problems with this faulty xml structure when adding layers programmaticaly to the runtime map. The layers where added correctly but the AJAX viewer doesn't respond anymore. I've got no error message an even no log entries in error.log so that it tooks me a while to figure out the problem.

[jng]

I can't see the real problem here. Groups are processed visually top-down (both Maestro and the Viewer).

Despite Folder_2 being "on top" of Folder_A, it is still a child of Folder_A. There is no concept of Draw Order for layer groups so I can't see where that particular XML order is going to be a problem.

The key thing to watch out for is empty/invalid parent group references. This is what kills a runtime map most of the time.

[gBecker]

OK, although it would be nice to have a clear structure in XML it seems to be a problem with my code. I've got a clue now!