Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Wrong call in EventsBehavior.cs ?
See original GitHub issueI stumbled upon a pretty subtle but from my point of view just wrong behaviour. Inside of EventsBehavior.cs is a check if a mouse movement occurred. After that in line 56 there is a invokation of OnMouseClick where I would rather expect OnMouseUp because it is the event handler of the MouseUp event. This “wrong” event call leads to some weird behaviour in our application. I was also able to verify that this is the problem by unregistering the EventsBehavior from the diagram.
Is this just wrong or is there more to this call?
Issue Analytics
- State:
- Created a year ago
- Comments:13
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Indeed, now that you’ve explained the issue, I see it clearly. MouseUp shouldn’t fire a MouseClick unless MouseDown happened as well, otherwise something like you described (clicking outside, moving then releasing) would trigger a click when it shouldn’t!
I will take a look at you rexample.
It will be fixed in the new major version. Would you like a quick fix for it with the current version? I can write you a modified EventsBehavior.