Closed MattReimer closed 2 years ago
Note: this is not a duplicate of #19
This bug refers to weird behaviour that isn't captured by the bugs specified in #19 so I'm going to keep it open
This is a really, really high priority.
@MattReimer #19 has been updated with specifics for the "final word on layer ordering".
This issue is now 5 months old and still has no specifics associated with it. I am removing from milestone RAVE 0.7 until there are specifics. Hopefully #19 fixes any lingering issues and we can put layer ordering behind us.
@philipbaileynar as mentioned above this is not actually anything to do with #19 (other than it references layers).
This is about erratic behaviour and the differences between intention and desired outcome when manipulating the layers.
I agree that it lacks reproducibility so I'm going to close it. We can always open a new ticket once we have screenshots or a video
I'm putting this issue here to start tracking evidence. Sometimes it seems like when you add a layer to the map the layer goes into the right hierarchy and group but the layer may be in the wrong order relative to its peers.
Reproducibility seems a bit squidgy on this so post below if you have steps.
One thing to consider is that if you do any manual re-ordering in the tree the plugin might have trouble figuring out where it's supposed to put the layer it's trying to add.