Number input advanced mode is not working in JP keyboard #75047

New Issue

Kinouti Takahiro · 2020-03-24T04:10:04+01:00

Kinouti Takahiro commented

2020-03-24 04:10:04 +01:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: 67EF:CF ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12028.2

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: 77d23b0bd7
Worked: (optional)

Short description of error
Number input advanced mode is not working in JP keyboard.

Exact steps for others to reproduce the error
In any transformation, before you type a numeric value, press the equal key (=) in your keyboard enter advanced mode.
But it does not work in JP keyboard. It seems to be involved that you need to hold shift to input = in JP keyboard.

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: 67EF:CF ATI Technologies Inc. 4.5.13559 Core Profile Context 26.20.12028.2 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash: `77d23b0bd7` Worked: (optional) **Short description of error** Number input advanced mode is not working in JP keyboard. **Exact steps for others to reproduce the error** In any transformation, before you type a numeric value, press the equal key (=) in your keyboard enter advanced mode. But it does not work in JP keyboard. It seems to be involved that you need to hold shift to input = in JP keyboard.

Kinouti Takahiro commented

2020-03-24 04:10:04 +01:00

Added subscriber: @dskjal-1

Sebastian Parborg commented

2020-03-24 11:55:33 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2020-03-24 11:55:33 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Sebastian Parborg commented

2020-03-24 11:55:33 +01:00

I have a Swedish keyboard layout where you also have to hold shift to be able to get into advanced mode and it seems to work fine for me.
This might be because I'm using Linux though... So this might be a Windows specific bug.

Exactly what does it do when you type =? It just eats the input or what?

I have a Swedish keyboard layout where you also have to hold shift to be able to get into advanced mode and it seems to work fine for me. This might be because I'm using Linux though... So this might be a Windows specific bug. Exactly what does it do when you type `=`? It just eats the input or what?

Kinouti Takahiro commented

2020-03-24 12:08:43 +01:00

On a JP keyboard - and = are same key. When press hold plus -, it inputs -.

Julian Eisel commented

2020-03-24 12:32:47 +01:00

Added subscriber: @JulianEisel

Julian Eisel commented

2020-03-24 12:32:47 +01:00

Just tested on Windows with a German keyboard (= is {nav Shift + 0} there), but couldn't recreate it either.

You can check what is output to the console when entering = after starting Blender with --debug-handlers.

Just tested on Windows with a German keyboard (`=` is {nav Shift + 0} there), but couldn't recreate it either. You can check what is output to the console when entering `=` after starting Blender with `--debug-handlers`.

Julian Eisel commented

2020-03-24 12:36:26 +01:00

Another thing, do you have IME activated? It could be that the IME interferes, even if the window doesn't actually become visible. IIRC it's a separate window for the OS, and there are known issues with modifier keys not working properly with window activation.

Sebastian Parborg commented

2020-03-24 12:37:38 +01:00

I also did a double check with linux and switched to the Japanese "OADG109A" layout and it still seems to work fine if I hit {nav Shift + -}.

I'm guessing that you are also using this OADG 109A layout?
https://en.wikipedia.org/wiki/Language_input_keys#Keys_for_Japanese_Keyboards

I also did a double check with linux and switched to the Japanese "OADG109A" layout and it still seems to work fine if I hit {nav Shift + -}. I'm guessing that you are also using this OADG 109A layout? https://en.wikipedia.org/wiki/Language_input_keys#Keys_for_Japanese_Keyboards

Kinouti Takahiro commented

2020-03-24 12:52:18 +01:00

I'm using OADG 109A layout. On Windows, it is displayed as 日本語キーボード(106/109 キー).

This is event log when shift + - is pressed. IME is not activated.

wm_event_do_handlers: Handling event
wmEvent type:103 / G, val:2 / RELEASE,

       shift:0, ctrl:0, alt:0, oskey:0, keymodifier:0,
       mouse:(1044,701), ascii:' ', utf8:'', keymap_idname:(null), pointer:0000028166F8C658

wm_event_do_handlers: Handling event
wmEvent type:217 / LEFT_SHIFT, val:1 / PRESS,

       shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0,
       mouse:(1044,701), ascii:' ', utf8:'', keymap_idname:(null), pointer:0000028166F8E278

wm_event_do_handlers: Handling event
wmEvent type:230 / MINUS, val:1 / PRESS,

       shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0,
       mouse:(1044,701), ascii:'=', utf8:'=', keymap_idname:(null), pointer:0000028166F8DA98

wm_event_do_handlers: Handling event
wmEvent type:230 / MINUS, val:2 / RELEASE,

       shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0,
       mouse:(1044,701), ascii:' ', utf8:'', keymap_idname:(null), pointer:0000028166F8D618

I'm using OADG 109A layout. On Windows, it is displayed as 日本語キーボード(106/109 キー). This is event log when shift + - is pressed. IME is not activated. wm_event_do_handlers: Handling event wmEvent type:103 / G, val:2 / RELEASE, ``` shift:0, ctrl:0, alt:0, oskey:0, keymodifier:0, mouse:(1044,701), ascii:' ', utf8:'', keymap_idname:(null), pointer:0000028166F8C658 ``` wm_event_do_handlers: Handling event wmEvent type:217 / LEFT_SHIFT, val:1 / PRESS, ``` shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, mouse:(1044,701), ascii:' ', utf8:'', keymap_idname:(null), pointer:0000028166F8E278 ``` wm_event_do_handlers: Handling event wmEvent type:230 / MINUS, val:1 / PRESS, ``` shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, mouse:(1044,701), ascii:'=', utf8:'=', keymap_idname:(null), pointer:0000028166F8DA98 ``` wm_event_do_handlers: Handling event wmEvent type:230 / MINUS, val:2 / RELEASE, ``` shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, mouse:(1044,701), ascii:' ', utf8:'', keymap_idname:(null), pointer:0000028166F8D618

Kinouti Takahiro commented

2020-03-24 13:02:06 +01:00

On US layout, works fine.

Sebastian Parborg commented

2020-03-24 13:51:58 +01:00

Hmm at first glance, it seems like this should be correct if I compare the output from my Swedish layout:

wm_event_do_handlers: Handling event
wmEvent  type:216 / RIGHT_SHIFT, val:1 / PRESS,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(291,614), ascii:'', utf8:'', pointer:0x7fb50ca69408

wm_event_do_handlers: Handling event
wmEvent  type:48 / ZERO, val:1 / PRESS,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(291,614), ascii:'=', utf8:'=', pointer:0x7fb50ca69408

wm_event_do_handlers: Handling event
wmEvent  type:48 / ZERO, val:2 / RELEASE,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(291,614), ascii:'', utf8:'', pointer:0x7fb50ca69408

wm_event_do_handlers: Handling event
wmEvent  type:216 / RIGHT_SHIFT, val:2 / RELEASE,
         shift:0, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(291,614), ascii:'', utf8:'', pointer:0x7fb50ca69408

But if I switch to the Japanese layout I get this:

wm_event_do_handlers: Handling event
wmEvent  type:217 / LEFT_SHIFT, val:1 / PRESS,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(235,506), ascii:'', utf8:'', pointer:0x7f5911ee0708

wm_event_do_handlers: Handling event
wmEvent  type:234 / EQUAL, val:1 / PRESS,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(235,506), ascii:'=', utf8:'=', pointer:0x7f5911ee0708

wm_event_do_handlers: Handling event
wmEvent  type:234 / EQUAL, val:2 / RELEASE,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(235,506), ascii:'', utf8:'', pointer:0x7f5911ee0708

wm_event_do_handlers: Handling event
wmEvent  type:217 / LEFT_SHIFT, val:2 / RELEASE,
         shift:0, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(235,506), ascii:'', utf8:'', pointer:0x7f5911ee0708

wm_event_do_handlers: Handling event
wmEvent  type:230 / MINUS, val:1 / PRESS,
         shift:0, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(235,506), ascii:'-', utf8:'-', pointer:0x7f5911ee0708

As you can see mine does not report the key as "MINUS" when holding shift but instead says that it is "EQUAL".
Perhaps the input is taken as "MINUS" for you then even if you hold shift?
Can you see if you can negate the number input in basic mode by doing shift+-?

Hmm at first glance, it seems like this should be correct if I compare the output from my Swedish layout: ``` wm_event_do_handlers: Handling event wmEvent type:216 / RIGHT_SHIFT, val:1 / PRESS, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(291,614), ascii:'', utf8:'', pointer:0x7fb50ca69408 wm_event_do_handlers: Handling event wmEvent type:48 / ZERO, val:1 / PRESS, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(291,614), ascii:'=', utf8:'=', pointer:0x7fb50ca69408 wm_event_do_handlers: Handling event wmEvent type:48 / ZERO, val:2 / RELEASE, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(291,614), ascii:'', utf8:'', pointer:0x7fb50ca69408 wm_event_do_handlers: Handling event wmEvent type:216 / RIGHT_SHIFT, val:2 / RELEASE, shift:0, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(291,614), ascii:'', utf8:'', pointer:0x7fb50ca69408 ``` But if I switch to the Japanese layout I get this: ``` wm_event_do_handlers: Handling event wmEvent type:217 / LEFT_SHIFT, val:1 / PRESS, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(235,506), ascii:'', utf8:'', pointer:0x7f5911ee0708 wm_event_do_handlers: Handling event wmEvent type:234 / EQUAL, val:1 / PRESS, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(235,506), ascii:'=', utf8:'=', pointer:0x7f5911ee0708 wm_event_do_handlers: Handling event wmEvent type:234 / EQUAL, val:2 / RELEASE, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(235,506), ascii:'', utf8:'', pointer:0x7f5911ee0708 wm_event_do_handlers: Handling event wmEvent type:217 / LEFT_SHIFT, val:2 / RELEASE, shift:0, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(235,506), ascii:'', utf8:'', pointer:0x7f5911ee0708 wm_event_do_handlers: Handling event wmEvent type:230 / MINUS, val:1 / PRESS, shift:0, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(235,506), ascii:'-', utf8:'-', pointer:0x7f5911ee0708 ``` As you can see mine does not report the key as "MINUS" when holding shift but instead says that it is "EQUAL". Perhaps the input is taken as "MINUS" for you then even if you hold shift? Can you see if you can negate the number input in basic mode by doing `shift+-`?

Kinouti Takahiro commented

2020-03-24 14:02:58 +01:00

Input can be negated in basic mode by doing shift+-.

Sebastian Parborg commented

2020-03-24 17:46:13 +01:00

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Sebastian Parborg commented

2020-03-24 17:46:13 +01:00

I'll see if I can spot the issue in the code if it is a simple one.
But we will probably need someone that experiences this issue to fix it, as we can't really test out if it works or not ourselves currently.

I'll see if I can spot the issue in the code if it is a simple one. But we will probably need someone that experiences this issue to fix it, as we can't really test out if it works or not ourselves currently.

Sebastian Parborg commented

2020-03-24 18:24:51 +01:00

@dskjal-1 Can you try this patch and see if it makes you able to go into advanced mode?
(It should also remove the ability to negate in basic mode too...)

test.patch

@dskjal-1 Can you try this patch and see if it makes you able to go into advanced mode? (It should also remove the ability to negate in basic mode too...) [test.patch](https://archive.blender.org/developer/F8427160/test.patch)

Sebastian Parborg commented

2020-03-24 18:41:01 +01:00

I also noticed something in the code:
You can also enter advanced mode with *. So I guess that one should work for you?

I also noticed something in the code: You can also enter advanced mode with `*`. So I guess that one should work for you?

Kinouti Takahiro commented

2020-03-24 18:45:41 +01:00

'*' works fine. Thanks!