Pass pointer events into on[Hover/Active/Focus]Change

[wrangelvid]

Pass pointer events into on[Hover/Active/Focus]Change

[bbohlender]

I think normal onPointerOver events are a better fit for this use case. on[X]Change are currently really just listeners for the respective signals used under the hood to have the respective conditional properties

[wrangelvid]

I should've been more precise in requesting this only for onHoverChange, onActiveChange and onFocusChange and not all conditionals. The Interactivity tutorial states that all UI elements can receive events like other r3f elements but extends it with hover and active. That implication makes it natural to include the pointer events into these. Then the Event Properties could document on[Hover/Active/Focus]Change while hover, active, and focus remain in the conditionals.

[bbohlender]

onHoverChange etc should imo not receive an event because that leads people to believe onHoverChange is a combination of onPointerOver & onPointerOut. However, the hover state is much more complex as it tracks the amount of pointer that are currently hovering and only changes the hover state if the amount is or is not greater than 0.

Your example use case is not fitting here, because in a case where the user is hovering with 1 pointer where no additional button is pressed and then also hovering with another pointer (e.g. controller) with a specific button pressed onHoverChange is only executed initially and only the initial event would be provided. Therefore the developer would not be notified of the second pointer and its event. This illustrates my point where I fear that people can confuse onHoverChange etc with the actual pointer event which is what should be used for your presented use case.

If you find a use case where having the initial and last event for the hover etc. change is necassary, please let me know :)

[wrangelvid]

That makes sense, thank you for the clarification.