We need to implement the behavior for mouseDown/mouseUp and mouseDragged in order to allow for views to properly track mouse events on a mouse click. Here is an example use case:
Let's say I have a view that I want to drag around the screen on click but the view snaps to a grid system meaning that the won't immediately move with the mouse until the mouse reaches the next grid boundary. On mouseDown, the view receiving the mouseDown needs to receive mouse move events and then a mouse up when the button is received even if the mouse is outside of the view boundary.
The way this is implemented in 1.6 (and every other desktop framework) is that the view responding true to the mouseDown() event will receive mouseDragged() event whenever the mouse moves regardless of mouse location. Likewise when the mouse button is released, that view will receive a mouseUp() event regardless of mouse location.
We need to re-implement this behavior is SC 2.0
We need to implement the behavior for mouseDown/mouseUp and mouseDragged in order to allow for views to properly track mouse events on a mouse click. Here is an example use case:
Let's say I have a view that I want to drag around the screen on click but the view snaps to a grid system meaning that the won't immediately move with the mouse until the mouse reaches the next grid boundary. On mouseDown, the view receiving the mouseDown needs to receive mouse move events and then a mouse up when the button is received even if the mouse is outside of the view boundary.
The way this is implemented in 1.6 (and every other desktop framework) is that the view responding true to the mouseDown() event will receive mouseDragged() event whenever the mouse moves regardless of mouse location. Likewise when the mouse button is released, that view will receive a mouseUp() event regardless of mouse location.
We need to re-implement this behavior is SC 2.0