Kerbal Space Program

Even the stock game is affected- when typing a craft's name into the top of the VAB, space will reset the camera and enter will reset ALL your staging- infuriating! X and C alter symmetry options too.

As for mods, it's not just Kerbal Alarm Clock, also affects MechJeb and any other mod that allows text input.

seems to be a general UI event bubbling issue- clicking too quickly on various UI elements passes double click events through, eg if you're trying to drop a maneuver node or scrolling through kerbals too quickly, the game will un-set your target because it can't tell the difference between clicking on a button a few times and a double click event.

This is especially annoying in the VAB when setting up staging, I have to deliberately go slow to avoid double click events even though I'm moving the mouse and clicking on different elements each time

I can confirm this. The UI does not seem to set selected elements to block inputs to other parts of the game. Entering numbers during flight is problem if you have any action groups set up. This has been a problem at lest since 0.20.2.

triffid_hunter: the double clicking issue seems to be not connected. Can you please check if it's dependent on your window managers mouse settings, and if it persists open a separate ticket?

I can confirm that pressing enter when the focus is in the text box below the craft name in the VAB triggers both a newline in text box as well as trigger the reset button in the bottom right. However, I cannot confirm the triggering of 'x', 'c' or space quick actions either in the craft name box nor the description box below it with 0.21.1 stock. The later may be due to the plugins.

still present in 0.23

This also affects the text entry box in the VAB for the name and description of the craft, as well as using up and down buttons or the mouse scroll wheel in windows, including the stock menus.

It's not just affecting mods, so it probably should be given higher priority. (It doesn't cause the game to be unplayable, so it probably should be considered medium priority, not high or critical.)

It is definately more annoying with mods.

This Issue is still very much alive in 0.25 and breaks the game when in use with any mod that requires any data entry. The bug shouldn't be on low priority.

I have created Bug #3437 to cover this more comprehensively and to update it to 0.25. I also included some examples how to reproduce the issues and how KSP should behave instead.

drluke wrote:

This Issue is still very much alive in 0.25 and breaks the game when in use with any mod that requires any data entry. The bug shouldn't be on low priority.

Agreed. This makes playing with text-input mods pretty unplayable. As well as wanting to add any sort of meaningful description to sub-assemblies, vehicle descriptions.

+1 to bump up the priority on this, or at least provide a workaround.

The issue remains in version 0.90. It makes it difficult to use any mod that requires data entry. Why is this a LOW priority? Please fix this bug. Thanks

I'd like to see this rectified as well. The double-click pass through is particularly annoying, and I haven't been able to implement a work-around, as the clickCount field in KSP's Mouse class is read-only.