MouseLeave needs to fire *before* MouseEntered for Adjacent GUI elements

[Shedletsky]

I have a hand of cards.

I have wired up events such that the mouse cursor changes to a pointer when it is inside the bounds of a card GUI element.

Outside of the card GUI elements, I want the cursor to be an open hand.

If I overlap my cards, I am having problems because MouseEnter on the adjacent card is firing before MouseLeave fires on the card that I am leaving. I believe MouseLeave should always fire first, otherwise complicated GUI state management logic is going to be needed to accomplish what I want.

[Sharksie]

This fix is in progress.

[Shedletsky]

Fastest fix ever.

[Shedletsky]

Is it firing in the order I connect the handlers right now?

[Shedletsky]

Just checked it’s not.

It’s intentionally firing in the wrong order.

[Sharksie]

It was already in progress

Along with a bunch of other gui/input-related fixes. Soon TM

@Shedletsky

Is it firing in the order I connect the handlers right now?

I think it fires in child order AKA undefined.

[Shedletsky]

ZIndex fixes too?

GUI Objects Should Calculate ZIndex Relative to their Parent

I have a TextLabel under an ImageLabel in the Explorer Both have ZIndex set to the default (1). If I set the ZIndex of the ImageLabel to be 10, it now draws on top of the TextLabel. I think this is wrong. Since the TextLabel is a child of the ImageLabel, it should have ZIndex 10 (inherited from parent) + 1 (it’s own default ZIndex). If I wanted the current behavior (no inheritance of ZIndex), I would make them siblings. At the moment if I want to create a GUI out of a bunch of elements and …

[Sharksie]

That one is a bit more involved. It would require new gui rendering code since it’s all based on the layer collector right now. It’s a conversation but I don’t see any reason it couldn’t be done, so maybe. I’m no rendering engineer though.