As of 2.3.0 on KSP 0.24, I cannot get numeric keypad input in any of the boxes.

This is particularly difficult because I use the numeric keypad as a workaround for the issue with issue of text boxes not stopping keypress passthrough on Linux. (This is a bug in Unity, although there might be a workaround it would have to be implemented in every mod.)

I would expect, that when number lock is on, I could enter numbers in the text boxes like I could in previous versions. Hopefully you can fix this in a future release.

Thanks.

Using Debian (jessie) I see none of these issues, numeric pad works fine
and I can but one text box over the other and only the top one receives
input.

I'd just assumed for once Unity actually had a bug fix

Long and short this must be Distro or even installation specific -
Unlike other "features" of unity I've not had to apply any work around
for input to work as it should.

Best
Chris

On 19/07/14 03:15, Ruedii wrote:

As of 2.3.0 on KSP 0.24, I cannot get numeric keypad input in any of
the boxes.

This is particularly difficult because I use the numeric keypad as a
workaround for the issue with issue of text boxes not stopping
keypress passthrough on Linux. (This is a bug in Unity, although there
might be a workaround it would have to be implemented in every mod.)

I would expect, that when number lock is on, I could enter numbers in
the text boxes like I could in previous versions. Hopefully you can
fix this in a future release.

Thanks.

—
Reply to this email directly or view it on GitHub
#391.

Sorry for this - but after an update I too have no working number pad.

However, I believe this is be a KSP/Unity bug and not a MechJeb bug as
Craft names
allow numeric characters but not using the number pad with numlock on

On 19/07/14 03:15, Ruedii wrote:

As of 2.3.0 on KSP 0.24, I cannot get numeric keypad input in any of
the boxes.

This is particularly difficult because I use the numeric keypad as a
workaround for the issue with issue of text boxes not stopping
keypress passthrough on Linux. (This is a bug in Unity, although there
might be a workaround it would have to be implemented in every mod.)

I would expect, that when number lock is on, I could enter numbers in
the text boxes like I could in previous versions. Hopefully you can
fix this in a future release.

Thanks.

—
Reply to this email directly or view it on GitHub
#391.

Yes, KSP/unity handle the text input. This is not a MJ bug.

As of the type-through. I'm talking about keys pressed while typing in an input box, going through to the main KSP input (for instance, if you type a "." on the main keyboard it will also advance time warp, or if you type an "s" it will nose-up your ship. ("s" is used to indicate seconds.)

Since this is a Unity Bug, should I add finding a workaround as a "feature request" since it clearly is not a bug in MechJeb. More accurately, creating a way to workaround Unity Widget and input bugs in general. (This is has been a recurring problem, and thus justifies fixing.)

Due to the way keyboard input is handled on Linux it's likely the keypad bug only affects some players. This is because some Desktop Environment setups wrap keypad text input through the Universal Input Method / Internationalization engine, and others don't. I'm running KDE without Universal Input Method keyboard support. I should see if turning on the Universal Input Method support or changing my desktop environment to XFCE, which uses the same input stack as Gnome, will change this. (I still like KDE enough to put up with the bug.) UIM functions have some other nice features that I might like, so it might be worth the added resources and latencies.

Also, I've noticed another bug in KSP on Linux in 0.24 that may indicate a change in the input stack, which would explain the keypad issue.

Clicks also pass through GUI elements, even when you highlight a check box, it also registers the click on the main KSP screen, and KSP elements (such as the staging controls in the VAB.) I'm not sure if it also registers in layered windows. I simply haven't tried it.

This has nothing to do with mechjeb and I cannot begin to see any possible way mechjeb could work round it.

I'm running xfce on a light system and fairly sure I'm not running any additional input layer

These sorts of bugs will persist until the creators of unity believe enough in their tools to use them to build the SDK/editor with them and we get a Linux native editor - testing in a VM is no substitute for actual bare metal and a compile / reboot cycle just takes too long to debug things like obscure input bugs

The place to report this is the official KSP bug tracker
http://bugs.kerbalspaceprogram.com/projects/ksp/issues

sorry to put such a downer on your report but it really is going to the wrong place!

On 20 July 2014 06:51:17 BST, Ruedii [email protected] wrote:

As of the type-through. I'm talking about keys pressed while typing in
an input box, going through to the main KSP input (for instance, if you
type a "." on the main keyboard it will also advance time warp, or if
you type an "s" it will nose-up your ship. ("s" is used to indicate
seconds.)

Since this is a Unity Bug, should I add finding a workaround as a
"feature request" since it clearly is not a bug in MechJeb. More
accurately, creating a way to workaround Unity Widget and input bugs in
general. (This is has been a recurring problem, and thus justifies
fixing.)

Due to the way keyboard input is handled on Linux it's likely the
keypad bug only affects some players. This is because some Desktop
Environment setups wrap keypad text input through the Universal Input
Method / Internationalization engine, and others don't. I'm running
KDE without Universal Input Method keyboard support. I should see if
turning on the Universal Input Method support or changing my desktop
environment to XFCE, which uses the same input stack as Gnome, will
change this. (I still like KDE enough to put up with the bug.) UIM
functions have some other nice features that I might like, so it might
be worth the added resources and latencies.

Also, I've noticed another bug in KSP on Linux in 0.24 that may
indicate a change in the input stack, which would explain the keypad
issue.

Clicks also pass through GUI elements, even when you highlight a check
box, it also registers the click on the main KSP screen, and KSP
elements (such as the staging controls in the VAB.) I'm not sure if it
also registers in layered windows. I simply haven't tried it.

---

Reply to this email directly or view it on GitHub:
#391 (comment)

Sent from my Android device with K-9 Mail. Please excuse my brevity.

Hello,

I too experienced this problem. I found a temporary workaround, until the issue is fixed in its appropriate place: Just remap the action groups to the numpad keys (in the input settings in the main menu). Then use the numer row to type numbers into mechjeb and numpad to trigger the action groups.