Another GroupLayer bug?

JasonKnisley

I've noticed two possible bugs with GroupLayer so far.  The first, which I already saw reported, is the fact that layers added to a group layer after the group layer is added to the map don't show up unless you call groupLayer.Initialize()... Interestingly, even while they aren't on the map they do show up in the Legend control.

A second possible bug, which I haven't seen reported yet, is that map.MoveLayer seems to have a strange effect on the GroupLayer.  As a test I have a map with a LayerCollection of size 8, where my GroupLayer is at the last index.  If call map.MoveLayer(map.Layers.IndexOf(groupLayer), 0) and then call map.Layers.IndexOf(groupLayer) immediately after the result now says that it is at index 0, but it doesn't actually get moved.  This is reflected both visually (I can still see it as the topmost layer of the map) and in the legend control, where it's position also does not move.  If I then check the index again (via a button click that I added for the sole purpose debugging this issue) I see that the index is back to 7.  It's as if it successfully moves to the new index (albeit only for a fraction of a second) and then immediately moves back to the old index.

JasonKnisley

Jennifer,

You are correct, there is no error.  I was testing MoveLayer() on a whim and got caught by a feature in my own code... the particular widget I was testing it on has a primary layer (which is now a GroupLayer with the release of 2.3), and when this widget is in focus it forces its primary layer to the top of the map if it isn't there already.  I experienced this particular problem because I was testing the MoveTo() function on that GroupLayer while this widget was in focus, and so it kept undoing my attempt to move it.  Sorry for the erroneous report.