You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
It seems that it has to do with input events overloading your event queue. I managed to make things better by reducing key repeat delay and speed (I like to move fast around). Here's some info: https://hq.scene.ro/axiom-verge-key-repeat-bad.png … and https://hq.scene.ro/axiom-verge-key-repeat-good.png … Maybe it will help others.
I'm not entirely sure what you mean...does the movement, etc continue even after releasing the keys? @flibitijibibo
So I take it the game listens to key press/repeat events, stuffs them in a queue and then processes them in time. This would explain why my code doesn't show the same behavior: I simply listen to key up/down events and update an internal kbd state from update to update.
Yes, that's exactly what I meant. Sorry for the confusing lingo, I'm not a native english speaker.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
