If you have an MTScatterWidget on top of an MTKinetic widget, when you move the
MTScatterWidget it will continue to move (as if it has momentium). This is correct behavior.
However, if while the MTScatterWidget is moving due to MTKinetic you attempt to move it in a
different direction, the MTScatter will interpret the MTKinetic touch_move events as a "second
touch", and you will transform (zoom) the widget instead of just changing the direction of the
movement.
You can use the pictures.py example to see this in action. Just move a picture and while it is
moving attempt to move it again. It will zoom.
The expected fix to this is to have a way to identify MTKinetic events so that we know not to use
those when calling find_second_touch in MTScatter.