Hi! 

I'm using v0.5.2 and I'm experiencing an issue with the clicking speed required to perform a double-click action. It could be that the speed required for double-clicks is bound to the framerate of the program or similar, as I'm running on a high-refreshrate screen and if I spam LMB really fast (but then REALLY fast, with both hands) it tends to work after a few moments. Once I turn the monitor refresh rate down from 300hz to 60hz it immediately becomes doable (feels like how it is supposed to be). I'm not sure whether the program syncs to my monitor's refresh rate, but that'd also explain the significantly higher CPU usage (for rendering, that is) when at 300hz. 

NOTE: The refresh rate / framerate also impacts the movement speed when moving around the screen with WASD.

EDIT: The text-removal pace (when you hold backspace when trying to remove some text) also seems way higher than it should be.

Hello!

Yes, this is an issue tied to the refresh rate, as you've noticed. I intended this as a fix as internally, the default idling process of the program eats up the remainder of the main CPU core as a means to maintain a consistent framerate. As this was not acceptable, I decided to rely on VSync to time the application. This seemed like an acceptable alternative at the time because I only had a 60 - 75hz monitor. However, I completely neglected to think of people who have monitors with higher refresh-rates where the program would simply run faster on their computers, haha.

I'll see about fixing the timing using my own methods and pushing out a build tonight; apologies for that!