My favorites | Sign in
Project Home Downloads Issues
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 93: Kinetic touches being interpreted as second touch in MTScatter
2 people starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ----
Closed:  Aug 2009


 
Reported by webmas...@heartspring.org, Aug 26, 2009
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.

Aug 26, 2009
Project Member #1 rileydutton@gmail.com
(This is actually submitted by Riley, that is my work email address).
Aug 28, 2009
Project Member #2 txprog
This issue was closed by revision d7b1ce5d11.
Status: Fixed

Powered by Google Project Hosting