focus: mouse events stop on parent without mouse_input #52

underscorediscovery opened this Issue Sep 6, 2016 · 0 comments


None yet

1 participant

underscorediscovery commented Sep 6, 2016 edited

If you have:

  • control (no mouse input)
    • control (mouse input)

The mouse propagation model would look for the highest control, and along the way would check for mouse input before continuing. This created #49 , #44 , #37 , and other issues, where the top control won't get the events it's meant to.

The correct approach is to get the highest control without caring for mouse input, the walking back up the parents looking for the first one that does have mouse input.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment