This design means that we will not be able to reliably obtain button state from outside of mouse events (e.g. from something that happens via a timer or otherwise async.) using Fit.Events.GetPointerState().
This seems like a bug or at least poor design. See if we can get rid of it.
IMPORTANT: Make sure this works properly if mouse/finger is moved outside of viewport at some point.
See https://github.com/Jemt/Fit.UI/blob/23ce04121c17f56660c64d469602cd3e26eb0adc/Core/Events.js#L796
This does not seem right. Why would we reset the state of the mouse buttons or the target on which a mouse event occurred when the mouse leaves that particular element? We do not do this for the OnTouchMove event: https://github.com/Jemt/Fit.UI/blob/23ce04121c17f56660c64d469602cd3e26eb0adc/Core/Events.js#L863
This design means that we will not be able to reliably obtain button state from outside of mouse events (e.g. from something that happens via a timer or otherwise async.) using Fit.Events.GetPointerState().
This seems like a bug or at least poor design. See if we can get rid of it.
IMPORTANT: Make sure this works properly if mouse/finger is moved outside of viewport at some point.