Skip to content
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

InteractionData bubbling? #1252

Closed
mustyoshi opened this issue Dec 5, 2014 · 6 comments
Closed

InteractionData bubbling? #1252

mustyoshi opened this issue Dec 5, 2014 · 6 comments
Labels
🙏 Feature Request Community request for new features, APIs, packages.
Milestone

Comments

@mustyoshi
Copy link

Perhaps add a way to stop the mouse event from continuing after it triggers a callback, and perhaps let the user specify what direction they want the events to propagate (descendants first, or ancestors first)

I almost achieved what I wanted by reversing the InteractionManager loops, except it ends after one iteration because the sprite doesn't have any interactive children. Hopefully that won't bite me, eh?

Idk how to add labels or I would have labeled it feature-request

@englercj englercj added the 🙏 Feature Request Community request for new features, APIs, packages. label Dec 5, 2014
@englercj
Copy link
Member

englercj commented Dec 5, 2014

If we convert InteractionManager to use events instead of raw callbacks we get some of this for free.

@lukejagodzinski
Copy link

It's what I'm looking for. I've created issue about the same problem #1291

@lukejagodzinski
Copy link

I've made this fix https://gist.github.com/jagi/4832f5f7255b7cc1d600 to make it work for mouse events in my project. However it's not perfect solution. It probably stops propagation to often in non mouse click events (for instance mouseout event). However I don't know why rebuildInteractiveGraphfunction is always putting Stage on top of the interactive items queue. It's definitely error. There is no reason to put in on top because it's the lowest layer.

@lukejagodzinski
Copy link

Unfortunately my fix breaks something with detecting mouseout event on Stage object. I don't fully understand how PIXI's layers order can influence hit area of object.

@englercj englercj mentioned this issue Dec 26, 2014
@englercj englercj added this to the v3.0 milestone Jan 8, 2015
@GoodBoyDigital
Copy link
Member

This should work now in v3. enjoy :) 👍

@lock
Copy link

lock bot commented Feb 26, 2019

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.

@lock lock bot locked and limited conversation to collaborators Feb 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🙏 Feature Request Community request for new features, APIs, packages.
Projects
None yet
Development

No branches or pull requests

4 participants