You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 19, 2022. It is now read-only.
As long as the #29 remains fixed when doing so, I think it would be best to revert behaviour so that the mousedown and mouseup don't need to be in the same location. The game will still likely do as the user intends in the vast majority of cases. So I don't see the need of going to the trouble of making sure the mouseup is within a certain radius of the mousedown.
It now pumps mousedown events on focus gained, maximized, etc. This will hopefully keep everything in #29 fixed. However, I feel like once or twice out of dozens of times when I was fixing it, I had the case of the mousedown event coming after the resize/maximize event (and not being in the queue at the same time). I couldn't get that to happen this time, but if any of you can make the bug manifest still I'd be interested.
Since fixing #29, mouse clicks require a "down" and "up" event in exactly the same location.
As mentioned in #60, this can make it feel unresponsive at times. I suspect this is also related to #59.
Perhaps there should be an area around each click the mouse can move within, or perhaps the behavior should return to ignoring mouse movement.
The text was updated successfully, but these errors were encountered: