Maestro 3.1 - dragging new layer group to top of list makes it disappear

[jbirch]

Steps to reproduce:

• Open Map Definition
• Click on button to add new layer group
• Drag new layer group to top of Layers by Group list and release
• *poof*

[jbirch]

Hmm. It didn't disappear, it moved it into the topmost layer group instead of inserting it above it.

[jng]

Ok the problem is that though visual indicators say you are dropping the layer group above the first layer group, the hit detection code says you are still dropping that layer group *inside* the first layer group, hence the result.

I'm going to try a 5px vertical buffer from the top of the TreeView, if the drop is made within this buffer, it is considered moving the group to the top.

[jng]

Now that I come to think of it, is ordering of layer groups even supported in the Map Definition Schema? If it was I would've put up/down arrows like the other toolbars.

[jbirch]

I've seen other weirdness with that "between" indicator; will try to make a mental note of *where* next time.

You can definitely order layer groups. I worked around it by editing as XML and moving chunks of text around :) There is some lack of flexibility in that layers outside of the layer groups always go after the layer groups and are ordered based on their draw order.

[jng]

But isn't Layer Group ordering essentially governed by the order in which Layers are processed in their draw order?

[jbirch]

Layer groups show up in the menu in the order they appear in the XML file, and before any layers. Layers themselves are displayed in their draw order, whether in groups or at the root of the menu.

[jng]

Re-iterating comment in #1761

Drag and drop re-ordering is not possible. This is due to dropping having two possible outcomes:

Dropping onto an actual group folder. This signifies to add the dropped item inside the group folder being dropped on. Dropping between two top-level group folders. This signifies to insert the dropped group between the two folders in the logical order.

Unfortunately, the tree control does not offer a usable way to detect drop type #2, despite showing the correct visuals. A suitable workaround is to use the new up/down buttons to re-arrange the logical group order.