I could care less if ZIndex was removed entirely, this problem was fixed, and nothing new was added.
I don’t see why anyone would want to use ZIndex at all. Using a system of “container” frames + the Child-Added order to determining the draw stacking (that is, cutting+repasting something to “move it to front” within a parent) works perfectly well for basically every use case as far as I can see. The only downside of that is that it’s not visible in the explorer what’s actually stacked on top (because the explorer items are not shown in child-added order), but if for your static UI you use a system of containers with only a handful of items in each one it’s easy / obvious what you had stacked in what order.
Obviously there ideally should be a more visible way to determine that ordering, but I don’t think that’s a very pressing issue, cutting and pasting items to change the draw order is easy enough and pretty intuitive too.
EDIT: For example, here’s my current gui: All of the frames are non-graphical, simply for layout / determining “ZOrdering” through child-added order. To get things to stack right I just place the dynamically created objects into the appropriate container frame and then they’ll all be stacked right… no need to manually fudge a bunch of ZIndicies.
