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

Interactivity "mouseup" callback #25

Closed
pc035860 opened this issue Mar 24, 2013 · 2 comments
Closed

Interactivity "mouseup" callback #25

pc035860 opened this issue Mar 24, 2013 · 2 comments

Comments

@pc035860
Copy link

It's kind of weird that the data presented in "mouseup" callback are the same with those presented in "mousedown" callback, which means I can't get any new information about the cursor when "mouseup" callback is called.

// in mousedown callback
{  // PIXI.InteractionData
    global: PIXI.Point with {x: 1037.6550910248598, y: 767.5979057591624},
    local: PIXI.Point with {x: 125.45961682745371, y: 160.0335078534032},
    target: PIXI.Sprite
}

// in mouseup callback
{  // PIXI.InteractionData
    global: PIXI.Point with {x: 1037.6550910248598, y: 767.5979057591624},
    local: PIXI.Point with {x: 125.45961682745371, y: 160.0335078534032},
    target: PIXI.Sprite
}
@GoodBoyDigital
Copy link
Member

Good catch! 👍 I just updated the InteractionManager so that the correct target is passed to mouseup. Thanks!

@lock
Copy link

lock bot commented Feb 27, 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 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants