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
touchendoutside events only gets dispatched for the first release. #2662
Comments
Added a touch counter instead of flag to ensure the correct touch count
Looks like you made a commit that fixed it for you. Can you retest this with the latest dev build and see if that has fixed your issue? You can see how to download the latest build in the FAQs. If it hasn't would you mind sending your fix as a PR? Thanks! |
… the correct touch count
Had this same issue, can confirm that this change fixes it. I tried making a pull request as well, thanks! |
…moved an extraneous line in InteractionManager.js
… the correct touch count
…moved an extraneous line in InteractionManager.js
* 'dev' of github.com:starakaj/pixi.js: Removed an unnecessary check for _touchCount === undefined, since the mixin for interactiveTarget will always set this See pixijs#2662 --- Added _touchCount to interactiveTarget.js, and removed an extraneous line in InteractionManager.js See pixijs#2662 --- bending to the will of eslint Fix issue pixijs#2662 Added a touch counter instead of flag to ensure the correct touch count
* Fix issue #2662 Added a touch counter instead of flag to ensure the correct touch count * See #2662 --- bending to the will of eslint * See #2662 --- Added _touchCount to interactiveTarget.js, and removed an extraneous line in InteractionManager.js * Removed an unnecessary check for _touchCount === undefined, since the mixin for interactiveTarget will always set this * Fix issue #2662 Added a touch counter instead of flag to ensure the correct touch count * See #2662 --- bending to the will of eslint * See #2662 --- Added _touchCount to interactiveTarget.js, and removed an extraneous line in InteractionManager.js * Removed an unnecessary check for _touchCount === undefined, since the mixin for interactiveTarget will always set this * Adding cancel events to interaction manager * Refactoring InteractionManager to normalize all events to PointerEvents. Also updated InteractiveTarget to handle multiple touch or pointer events by recording pointerId for all tracked events, rather than just counting events. Finally, InteractionManager now updates on all tracked events, rather than just mouse events, so it should send move events when UI objects move underneath any held event, not just the mouse * Typo: mouse is not a function * InteractionManager normalizeToPointerData now returns an array of normalized events for TouchEvents with multiple changedtouches * Typo: no such thing as onPointerStart * Fixing some more typos: trying to read the pointerId of un-normalized events * Typos: un-normalized events don't have a pointerType * Added identifier property to InteractionData, and got rid of some typos---trying to read pointerId from un-normalized events * Forgot to bind onPointerCancel * Refactoring interactiveTarget.js a bit, so that over, left down and right down are pointer properties, not mouse properties. * Forgot an export default * Changed the mixin pattern for Pixi.interaction.interactiveTarget, so that this is bound correctly, so that DisplayObjects can each get a unique object for tracking pointers * Fixed some typos, moved interactiveTarget back to being an object, and released InteractionData after touch up/cancelled events * Small fixed * Safari compatibility * hasOwnProperty fix * Safer to use a string for mouse pointer than a number * InteractionManager should now handle native DOM pointer events with pointerType mouse or touch by emitting mouse and touch events, respectively * InteractionManager test now respects the refactored spec for InteractionManager * Pointer events exclusive * String.startsWith is not available in all browsers esp. older version of Safari. As it's just used in one place we can use a RegExp here too * Moving from regex, slightly faster
* Fix issue #2662 Added a touch counter instead of flag to ensure the correct touch count * See #2662 --- bending to the will of eslint * See #2662 --- Added _touchCount to interactiveTarget.js, and removed an extraneous line in InteractionManager.js * Removed an unnecessary check for _touchCount === undefined, since the mixin for interactiveTarget will always set this * Fix issue #2662 Added a touch counter instead of flag to ensure the correct touch count * See #2662 --- bending to the will of eslint * See #2662 --- Added _touchCount to interactiveTarget.js, and removed an extraneous line in InteractionManager.js * Removed an unnecessary check for _touchCount === undefined, since the mixin for interactiveTarget will always set this * Adding cancel events to interaction manager * Refactoring InteractionManager to normalize all events to PointerEvents. Also updated InteractiveTarget to handle multiple touch or pointer events by recording pointerId for all tracked events, rather than just counting events. Finally, InteractionManager now updates on all tracked events, rather than just mouse events, so it should send move events when UI objects move underneath any held event, not just the mouse * Typo: mouse is not a function * InteractionManager normalizeToPointerData now returns an array of normalized events for TouchEvents with multiple changedtouches * Typo: no such thing as onPointerStart * Fixing some more typos: trying to read the pointerId of un-normalized events * Typos: un-normalized events don't have a pointerType * Added identifier property to InteractionData, and got rid of some typos---trying to read pointerId from un-normalized events * Forgot to bind onPointerCancel * Refactoring interactiveTarget.js a bit, so that over, left down and right down are pointer properties, not mouse properties. * Forgot an export default * Changed the mixin pattern for Pixi.interaction.interactiveTarget, so that this is bound correctly, so that DisplayObjects can each get a unique object for tracking pointers * Fixed some typos, moved interactiveTarget back to being an object, and released InteractionData after touch up/cancelled events * Small fixed * Safari compatibility * hasOwnProperty fix * Safer to use a string for mouse pointer than a number * InteractionManager should now handle native DOM pointer events with pointerType mouse or touch by emitting mouse and touch events, respectively * InteractionManager test now respects the refactored spec for InteractionManager * Pointer events exclusive * String.startsWith is not available in all browsers esp. older version of Safari. As it's just used in one place we can use a RegExp here too * Moving from regex, slightly faster * See #3149 --- Add support for touchcancel and pointercancel (#3375) * Fix issue #2662 Added a touch counter instead of flag to ensure the correct touch count * See #2662 --- bending to the will of eslint * See #2662 --- Added _touchCount to interactiveTarget.js, and removed an extraneous line in InteractionManager.js * Removed an unnecessary check for _touchCount === undefined, since the mixin for interactiveTarget will always set this * Fix issue #2662 Added a touch counter instead of flag to ensure the correct touch count * See #2662 --- bending to the will of eslint * See #2662 --- Added _touchCount to interactiveTarget.js, and removed an extraneous line in InteractionManager.js * Removed an unnecessary check for _touchCount === undefined, since the mixin for interactiveTarget will always set this * Adding cancel events to interaction manager * Refactoring InteractionManager to normalize all events to PointerEvents. Also updated InteractiveTarget to handle multiple touch or pointer events by recording pointerId for all tracked events, rather than just counting events. Finally, InteractionManager now updates on all tracked events, rather than just mouse events, so it should send move events when UI objects move underneath any held event, not just the mouse * Typo: mouse is not a function * InteractionManager normalizeToPointerData now returns an array of normalized events for TouchEvents with multiple changedtouches * Typo: no such thing as onPointerStart * Fixing some more typos: trying to read the pointerId of un-normalized events * Typos: un-normalized events don't have a pointerType * Added identifier property to InteractionData, and got rid of some typos---trying to read pointerId from un-normalized events * Forgot to bind onPointerCancel * Refactoring interactiveTarget.js a bit, so that over, left down and right down are pointer properties, not mouse properties. * Forgot an export default * Changed the mixin pattern for Pixi.interaction.interactiveTarget, so that this is bound correctly, so that DisplayObjects can each get a unique object for tracking pointers * Fixed some typos, moved interactiveTarget back to being an object, and released InteractionData after touch up/cancelled events * Small fixed * Safari compatibility * hasOwnProperty fix * Safer to use a string for mouse pointer than a number * InteractionManager should now handle native DOM pointer events with pointerType mouse or touch by emitting mouse and touch events, respectively * InteractionManager test now respects the refactored spec for InteractionManager * Pointer events exclusive * String.startsWith is not available in all browsers esp. older version of Safari. As it's just used in one place we can use a RegExp here too * Moving from regex, slightly faster * Fixed interaction tests for the new world of pointer events
Now that #3546 has been merged, this should be all set. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
In a multitouch application, when you touch an object with two fingers, and then drag off and release both fingers, the 'touchendoutside' event is only dispatched once.
http://stackoverflow.com/questions/37882401/pixijs-not-all-touchend-events-triggering-outside-of-displayobject?noredirect=1#comment63288886_37882401
The text was updated successfully, but these errors were encountered: