Picking out order

[NthTensor]

Tweaks picking docs slightly for formatting and to add additional context about the ordering of Over and Out events. Also shifts Out to trigger before Over in the global event ordering.

Because of how focus is tracked, we must send all Over and Out events at the same time, in a block. Originally I had Over precede Out in the global event order, because this seemed natural. However, the effect of this, when a pointer moves between entities, is to have the new entity receive Over before the old entity received Out, which several users found confusing.

The new ordering (out before over globally, over before out locally per entity) should make it much easier to write hover state cleanup code.

[alice-i-cecile]

Really excellent docs. I'd love to have some tests to verify that order, but that's a ton of extra work and I won't block on it.

[NthTensor]

I'd love to have some tests to verify that order, but that's a ton of extra work and I won't block on it.

ooh good idea. I think this will make sense to do as part of the next winit upgrade, because the way this pointer stuff interacts with their pointer stuff will be complex and not entirely owned by us.

[doup]

The comment on pointer presses might be wrong? I think it should say down/click/up. Apart from that the ordering explained at the beginning looks consistent with the code.

Btw, great docs 👍

[mockersf]

@NthTensor could you look into the conflict and fixing the order in the comment?

[NthTensor]

Yep, thanks for the poke.