Skip to content

event.touches and event.targetTouches #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
nomve opened this issue Mar 17, 2016 · 1 comment
Open

event.touches and event.targetTouches #55

nomve opened this issue Mar 17, 2016 · 1 comment
Milestone

Comments

@nomve
Copy link
Collaborator

nomve commented Mar 17, 2016

The eventobject currently has an input property that tells which input triggered a gesture. It is similar to targetTouches but not the same. Maybe rename to gestureInput.

targetTouches would be more difficult to implement than just touches. For touches, adapt tuioInput to also notify of all currently known input. The info is already there just not passed to a gesture.

TouchEvent.targetTouches Read only
A TouchList of all the Touch objects that are both currently in contact with the touch surface and were also started on the same element that is the target of the event.

TouchEvent.touches Read only
A TouchList of all the Touch objects representing all current points of contact with the surface, regardless of target or changed status.

@nomve nomve added this to the 0.8 milestone Mar 17, 2016
@nomve
Copy link
Collaborator Author

nomve commented Mar 17, 2016

also notifies about touches outside of the browser, which is wrong.

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

No branches or pull requests

1 participant