Shift-space doesn't type space in type-in fields (user expectation bug?) #47841

New Issue

Adrian Winchell · 2016-03-18T17:12:47+01:00

Adrian Winchell commented

2016-03-18 17:12:47 +01:00

System Information
Windows 10, nVidia GeForce GTX 550 Ti

Blender Version
Broken: 2.76b [f337fea] 2.77 test builds [431a5b6]
Worked: possibly never?

Short description of error
In any fields that allow keyboard entry- but NOT in the text editor or python console - having 'shift' held when pressing the space bar does not type a space. In the text editor or python console it does type a space, as expected. This is largely just a minor annoyance, as when I'm renaming bone hierarchies, I wind up missing spaces and creating bones that don't x-mirror properly.

Exact steps for others to reproduce the error
Open a new Blender file. In any means of renaming the default cube (viewport properties - [x] panel, double click its name in outliner, or object name display in object datablock section of Properties editor) attempt to give it a name that contains a space while holding down shift. (like doing all-caps manually, ie: "CUBE OF DOOM"). Same is true of any text-entry fields, even numeric fields (although it matters far less as these are evaluated when enter is pressed).

**System Information** Windows 10, nVidia GeForce GTX 550 Ti **Blender Version** Broken: 2.76b [f337fea] 2.77 test builds [431a5b6] Worked: possibly never? **Short description of error** In any fields that allow keyboard entry- but NOT in the text editor or python console - having 'shift' held when pressing the space bar does not type a space. In the text editor or python console it does type a space, as expected. This is largely just a minor annoyance, as when I'm renaming bone hierarchies, I wind up missing spaces and creating bones that don't x-mirror properly. **Exact steps for others to reproduce the error** Open a new Blender file. In any means of renaming the default cube (viewport properties - [x] panel, double click its name in outliner, or object name display in object datablock section of Properties editor) attempt to give it a name that contains a space while holding down shift. (like doing all-caps manually, ie: "CUBE OF DOOM"). Same is true of any text-entry fields, even numeric fields (although it matters far less as these are evaluated when enter is pressed).

Adrian Winchell commented

2016-03-18 17:12:47 +01:00

Changed status to: 'Open'

Adrian Winchell commented

2016-03-18 17:12:47 +01:00

Added subscriber: @snapai

Julian Eisel commented

2016-03-18 18:40:05 +01:00

Added subscribers: @MartijnBerger, @JulianEisel

Julian Eisel commented

2016-03-18 18:40:05 +01:00

Working fine here. IIRC, shift+space was used for activating IME (input method editor) though, for which we use a completely own backend on Windows. Maybe you use a non-Latin keyboard layout that has IME support? Also, just to be sure, you might want to check your keyboard layout settings and disable everything IME related.

@MartijnBerger, since this could really well be a Windows only issue, mind trying?

Working fine here. IIRC, shift+space was used for activating IME (input method editor) though, for which we use a completely own backend on Windows. Maybe you use a non-Latin keyboard layout that has IME support? Also, just to be sure, you might want to check your keyboard layout settings and disable everything IME related. @MartijnBerger, since this could really well be a Windows only issue, mind trying?

Adrian Winchell commented

2016-03-19 00:29:36 +01:00

I'm using a standard US keyboard layout, a Logitech K120, their basic wired QWERTY keyboard, on my Windows 10 desktop PC.

Same issue is present on my Lenovo X220T laptop running Windows 7 and using its built-in keyboard,

and on a relative's Dell Inspiron 3521 running Windows 8.1 on its built in keyboard.

All three are using default US English language system settings, and a standard US QWERTY keyboard.

Issue is not present on a MacBook 2010, this certainly appears to be a Windows-specific issue.

I'm using a standard US keyboard layout, a Logitech K120, their basic wired QWERTY keyboard, on my Windows 10 desktop PC. Same issue is present on my Lenovo X220T laptop running Windows 7 and using its built-in keyboard, and on a relative's Dell Inspiron 3521 running Windows 8.1 on its built in keyboard. All three are using default US English language system settings, and a standard US QWERTY keyboard. Issue is not present on a MacBook 2010, this certainly appears to be a Windows-specific issue.

Aaron Carlisle commented

2016-03-20 19:26:55 +01:00

Added subscriber: @Blendify