Can't type tilde (~) in text editing mode - Blender enters fly/walk navigation immediately #82492

New Issue

Ronan Paixão · 2020-11-07T19:17:02+01:00

Ronan Paixão commented

2020-11-07 19:17:02 +01:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71
OS Language: Brazilian Portuguese
Keyboard layout: United States (international)

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29
Worked: don't know

Short description of error
Using the ENG layout the tilde (~) is in this position on the keyboard:

It can be entered by pressing {key Shift `}.
However, this is the shortcut of another operator:

This conflict causes the VIEW3D_OT_navigate operator to run instead of the FONT_OT_text_insert.
Pressing {key Shift `} (grave accent) enters into fly/walk navigation even when in text editing mode. This makes it impossible to type letters with tilde (i.e. "ã") directly into Blender.
The workaround for now is typing the text I need in another program and then pasting into Blender.
This is quite annoying, specially for someone who speaks another language, or has the tilde in his name, even if one uses the English user interface.
This bug might be related to #66607.

Exact steps for others to reproduce the error

Open Blender with a new file.
Add a text object.
Enter text mode ({key TAB}).
Press {key Shift `}

This enters the fly/walk navigation mode immediately, instead of registering the tilde deadkey.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 456.71 OS Language: Brazilian Portuguese Keyboard layout: United States (international) **Blender Version** Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `0330d1af29` Worked: don't know **Short description of error** Using the `ENG` layout the tilde (~) is in this position on the keyboard: ![400px-KB_United_States-NoAltGr.svg.png](https://archive.blender.org/developer/F12831112/400px-KB_United_States-NoAltGr.svg.png) It can be entered by pressing {key Shift `}. However, this is the shortcut of another operator: ![untitled.png](https://archive.blender.org/developer/F9269382/untitled.png) This conflict causes the `VIEW3D_OT_navigate` operator to run instead of the `FONT_OT_text_insert`. Pressing {key Shift `} (grave accent) enters into fly/walk navigation even when in text editing mode. This makes it impossible to type letters with tilde (i.e. "**ã**") directly into Blender. The workaround for now is typing the text I need in another program and then pasting into Blender. This is quite annoying, specially for someone who speaks another language, or has the tilde in his name, even if one uses the English user interface. This bug might be related to #66607. **Exact steps for others to reproduce the error** - Open Blender with a new file. - Add a text object. - Enter text mode ({key TAB}). - Press {key Shift `} This enters the fly/walk navigation mode immediately, instead of registering the tilde deadkey.

Ronan Paixão commented

2020-11-07 19:17:02 +01:00

Added subscriber: @ronanpaixao

Richard Antalik commented

2020-11-10 22:04:16 +01:00

Added subscriber: @iss

Richard Antalik commented

2020-11-10 22:04:16 +01:00

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

Richard Antalik commented

2020-11-10 22:04:16 +01:00

I can't reproduce this with english keyboard layout. What layout do you use?

Ronan Paixão commented

2020-11-11 12:44:48 +01:00

As reported, my keyboard layout is (in free translation): United States (international).
The input method (language-layout), as reported by Windows, is:

Português (Brasil) - Estados Unidos (internacional)

The actual keyboard is the usual 104-key mechanical keyboard. Specifics and photos can be seen at the manufacturer's site: https://www.hoopson.com.br/produto/mj-70-teclado-mecanico/

To be more thorough, even though my Windows language is in Brazilian Portuguese, I keep my Blender language as English.

As reported, my keyboard layout is (in free translation): United States (international). The input method (language-layout), as reported by Windows, is: > Português (Brasil) - Estados Unidos (internacional) The actual keyboard is the usual 104-key mechanical keyboard. Specifics and photos can be seen at the manufacturer's site: https://www.hoopson.com.br/produto/mj-70-teclado-mecanico/ To be more thorough, even though my Windows language is in Brazilian Portuguese, I keep my Blender language as English.

Richard Antalik commented

2020-11-11 21:33:45 +01:00

I can't reproduce this even with portugese keyboard input, I am not sure if OS language would have influence there.

Can you check if this happens when you click on File > Defaults > Load Factory Settings?

Running Blender from console with --debug-events I don't see distinction between events whether I am in edit mode or object mode.
If you could check this out it would help us to see if there is some problem.

Edit mode:

wm_event_do_handlers: Handling event
wmEvent  type:217 / LEFT_SHIFT, val:1 / PRESS,
         prev_type:229 / ACCENT_GRAVE, prev_val:2 / RELEASE,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(535,441), ascii:'', utf8:'', pointer:0000027A68E14128

wm_event_do_handlers: Handling event
wmEvent  type:229 / ACCENT_GRAVE, val:1 / PRESS,
         prev_type:217 / LEFT_SHIFT, prev_val:2 / RELEASE,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(566,445), ascii:'~', utf8:'~', pointer:0000027A68E15E68

Object mode:

wm_event_do_handlers: Handling event
wmEvent  type:217 / LEFT_SHIFT, val:1 / PRESS,
         prev_type:217 / LEFT_SHIFT, prev_val:1 / PRESS,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(874,727), ascii:'', utf8:'', pointer:0000027A68E0FCE8

wm_event_do_handlers: Handling event
wmEvent  type:229 / ACCENT_GRAVE, val:1 / PRESS,
         prev_type:217 / LEFT_SHIFT, prev_val:2 / RELEASE,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(852,671), ascii:'~', utf8:'~', pointer:0000027A68E0F188

I can't reproduce this even with portugese keyboard input, I am not sure if OS language would have influence there. Can you check if this happens when you click on File > Defaults > Load Factory Settings? Running Blender from console with `--debug-events` I don't see distinction between events whether I am in edit mode or object mode. If you could check this out it would help us to see if there is some problem. Edit mode: ``` wm_event_do_handlers: Handling event wmEvent type:217 / LEFT_SHIFT, val:1 / PRESS, prev_type:229 / ACCENT_GRAVE, prev_val:2 / RELEASE, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(535,441), ascii:'', utf8:'', pointer:0000027A68E14128 wm_event_do_handlers: Handling event wmEvent type:229 / ACCENT_GRAVE, val:1 / PRESS, prev_type:217 / LEFT_SHIFT, prev_val:2 / RELEASE, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(566,445), ascii:'~', utf8:'~', pointer:0000027A68E15E68 ``` Object mode: ``` wm_event_do_handlers: Handling event wmEvent type:217 / LEFT_SHIFT, val:1 / PRESS, prev_type:217 / LEFT_SHIFT, prev_val:1 / PRESS, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(874,727), ascii:'', utf8:'', pointer:0000027A68E0FCE8 wm_event_do_handlers: Handling event wmEvent type:229 / ACCENT_GRAVE, val:1 / PRESS, prev_type:217 / LEFT_SHIFT, prev_val:2 / RELEASE, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(852,671), ascii:'~', utf8:'~', pointer:0000027A68E0F188 ```

Ronan Paixão commented

2020-11-12 18:17:50 +01:00

I did the load factory settings procedure, but nothing changed.

I dumped the output with --debug-events here:

blender_debug.txt

In this file, I created a "General" file, loaded factory defaults, added the text, pressed Shift+ (this entered fly mode), exited with `ESC`, entered edit mode with `Tab`, pressed `Shift`+ (this should result in a tilde deadkey but entered fly mode, hence the bug), and exited the program.

This might be related to another abnormal behavior I have noticed before, but haven't reported yet. When I'm in an explicitly text widget, I have to hold the shift key for around one second before hitting the grave accent key to get a tilde. If I don't wait (and one second is an awful lot of time when typing), I get the grave accent instead of the tilde.

I used your suggestion of the --debug-events flag again in this dump, in the hope that it will help the solution of this bug:

blender_debug2.txt

In this dump, I created a "General" file, when to the scripting view and started typing Shift+``` and then a, with different intervals. This should always result in ã, but unless I wait around one second between the shift and the accent, I get à, which is the same as not pressing the shift.

This is what resulted in the scripting file, before I closed the program:

ààãàãããààààã

I did the load factory settings procedure, but nothing changed. I dumped the output with `--debug-events` here: [blender_debug.txt](https://archive.blender.org/developer/F9267227/blender_debug.txt) In this file, I created a "General" file, loaded factory defaults, added the text, pressed `Shift`+``` (this entered fly mode), exited with `ESC`, entered edit mode with `Tab`, pressed `Shift`+``` (this should result in a tilde deadkey but entered fly mode, hence the bug), and exited the program. This might be related to another abnormal behavior I have noticed before, but haven't reported yet. When I'm in an explicitly text widget, I have to hold the `shift` key for around **one second** before hitting the grave accent key to get a tilde. If I don't wait (and one second is an awful lot of time when typing), I get the grave accent instead of the tilde. I used your suggestion of the `--debug-events` flag again in this dump, in the hope that it will help the solution of this bug: [blender_debug2.txt](https://archive.blender.org/developer/F9267266/blender_debug2.txt) In this dump, I created a "General" file, when to the scripting view and started typing `Shift`+``` and then `a`, with different intervals. This should always result in `ã`, but unless I wait around one second between the shift and the accent, I get `à`, which is the same as not pressing the shift. This is what resulted in the scripting file, before I closed the program: > ààãàãããààààã

Richard Antalik commented

2020-11-12 21:41:55 +01:00

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

Richard Antalik commented

2020-11-12 21:41:55 +01:00

Added subscriber: @mano-wii

Richard Antalik commented

2020-11-12 21:41:55 +01:00

This should be reported event for your Shift+` keypress

wm_event_do_handlers: Handling event
wmEvent  type:217 / LEFT_SHIFT, val:1 / PRESS,
         prev_type:219 / TAB, prev_val:1 / PRESS,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(793,530), ascii:' ', utf8:'', pointer:0000022308360998

wm_event_do_handlers: Handling event
wmEvent  type:229 / ACCENT_GRAVE, val:1 / PRESS,
         prev_type:219 / TAB, prev_val:2 / RELEASE,
         shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0,
         mouse:(793,530), ascii:' ', utf8:'', pointer:0000022308360488

There is difference to mine. I guess this could be same issue as #68577? Can you type ã in some textbox in Blender?

@mano-wii Can you reproduce this?

This should be reported event for your Shift+` keypress ``` wm_event_do_handlers: Handling event wmEvent type:217 / LEFT_SHIFT, val:1 / PRESS, prev_type:219 / TAB, prev_val:1 / PRESS, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(793,530), ascii:' ', utf8:'', pointer:0000022308360998 wm_event_do_handlers: Handling event wmEvent type:229 / ACCENT_GRAVE, val:1 / PRESS, prev_type:219 / TAB, prev_val:2 / RELEASE, shift:1, ctrl:0, alt:0, oskey:0, keymodifier:0, is_repeat:0, mouse:(793,530), ascii:' ', utf8:'', pointer:0000022308360488 ``` There is difference to mine. I guess this could be same issue as #68577? Can you type `ã` in some textbox in Blender? @mano-wii Can you reproduce this?

Germano Cavalcante commented

2020-11-12 22:57:56 +01:00

I can't reproduce the problem even with the OS in Portuguese and using the Brazilian Portuguese PTB layout for the keyboard.
By the way, I may be looking at the wrong place but by default there is no shortcut assigned to "Fly Navigation":

I can't reproduce the problem even with the OS in Portuguese and using the Brazilian Portuguese PTB layout for the keyboard. By the way, I may be looking at the wrong place but by default there is no shortcut assigned to "Fly Navigation": ![image.png](https://archive.blender.org/developer/F9269197/image.png)

Richard Antalik commented

2020-11-12 23:23:59 +01:00

It isn't in search, but there is shortcut

![untitled.png](https://archive.blender.org/developer/F9269382/untitled.png) It isn't in search, but there is shortcut

Germano Cavalcante commented

2020-11-12 23:42:28 +01:00

I had to check the ENG layout to find out where that tilde is.
In the Brazilian layout the position is totally different:

Anyway, I can't reproduce the problem even using the United States layout

I had to check the ENG layout to find out where that tilde is. In the Brazilian layout the position is totally different: ![image.png](https://archive.blender.org/developer/F9269496/image.png) Anyway, I can't reproduce the problem even using the United States layout

Richard Antalik commented

2020-11-13 00:03:04 +01:00

@ronanpaixao can you check if this happens with different keyboard?

Ronan Paixão commented

2020-11-13 03:31:17 +01:00

If I use the traditional ABNT2 Brazilian keyboard layout, the problem does not show up, especially considering that the tilde is in a different position like @mano-wii pointed out.

However, this would force me to use either an ABNT2 keyboard or just get used to the layout being different from the actual keyboard (and I did have quite a hard time actually getting a US keyboard, which I prefer, in Brazil).

Also, I actually have a cheapo ABNT2 keyboard and tested it. As said, it works fine with the ABNT2 layout, but if I switch the OS layout to United States (international), then the tilde will be "the key under ESC" and the bug persists.

I have also just noticed that not pressing Shift, which should get me the grave accent as a deadkey, also is buggy in that it does not give me the accent, but displays some kind of "Gizmo" menu, even though I'm still in text edit mode.

Some further tests showed me that

If I exit the fly mode by clicking with the mouse (not pressing ESC, Enter or another key) and then press a will get me the character I want. I think this is still a bug. And the 1-second-wait is still necessary too.
Text boxes in panels (I tested the object naming text box) and the scripting workspace (except the default upper-left 3D view) will work OK (though still get the 1-second bug).
For the 1-second bug, the left shift seems more susceptible, while the right shift seems to need less time to actually register.
"The key under ESC" events are only triggered when using the "United States (international)" layout (independent of US or ABNT2 physcial keyboards).
The option in Edit->Preferences->Keymap->Grave Accent / Tilde Action changes the incorrect "Gizmo menu" to a (also incorrect if in text-edit mode) "Navigation menu".
Actually, this option does not trigger the correct menu if I press the grave accent or tilde keys, even in object mode, if the ABNT2 layout is selected.

For me, it looks like "the key under ESC" is generating the fly/gizmo events even when in text-edit mode, where (in my opinion) it shouldn't.

If I use the traditional ABNT2 Brazilian keyboard layout, the problem does not show up, especially considering that the tilde is in a different position like @mano-wii pointed out. However, this would force me to use either an ABNT2 keyboard or just get used to the layout being different from the actual keyboard (and I did have quite a hard time actually getting a US keyboard, which I prefer, in Brazil). Also, I actually have a cheapo ABNT2 keyboard and tested it. As said, it works fine with the ABNT2 layout, but if I switch the OS layout to United States (international), then the tilde will be "the key under ESC" and the bug persists. I have also just noticed that not pressing `Shift`, which should get me the grave accent as a deadkey, also is buggy in that it does not give me the accent, but displays some kind of "Gizmo" menu, even though I'm still in text edit mode. Some further tests showed me that - If I exit the fly mode *by clicking with the mouse (not pressing `ESC`, `Enter` or another key) and then press `a`* will get me the character I want. I think this is still a bug. And the 1-second-wait is still necessary too. - Text boxes in panels (I tested the object naming text box) and the scripting workspace (except the default upper-left 3D view) will work OK (though still get the 1-second bug). - For the 1-second bug, the left shift seems more susceptible, while the right shift seems to need less time to actually register. - "The key under ESC" events are only triggered when using the "United States (international)" layout (independent of US or ABNT2 physcial keyboards). - The option in Edit->Preferences->Keymap->Grave Accent / Tilde Action changes the incorrect "Gizmo menu" to a (also incorrect if in text-edit mode) "Navigation menu". - Actually, this option does **not** trigger the correct menu if I press the grave accent or tilde keys, even in object mode, if the ABNT2 layout is selected. For me, it looks like "the key under ESC" is generating the fly/gizmo events even when in text-edit mode, where (in my opinion) it shouldn't.

Germano Cavalcante commented

2022-01-28 15:14:40 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Germano Cavalcante commented

2022-01-28 15:14:40 +01:00

Revisiting old bugs.
I can replicate now using Layout ENG.
But I believe this is a Known Issue as I'm not sure if it's possible to prioritize an operator when there is a conflict (FONT_OT_text_insert vs VIEW3D_OT_navigate).
In my opinion the FONT_OT_text_insert operator should always be executed first in these cases.

Revisiting old bugs. I can replicate now using Layout `ENG`. But I believe this is a `Known Issue` as I'm not sure if it's possible to prioritize an operator when there is a conflict (`FONT_OT_text_insert` vs `VIEW3D_OT_navigate`). In my opinion the `FONT_OT_text_insert` operator should always be executed first in these cases.

Germano Cavalcante changed title from ~~Can't type tilde in text editing mode - Blender enters fly/walk navigation immediately~~ to Can't type tilde (~) in text editing mode - Blender enters fly/walk navigation immediately

2022-01-28 15:21:35 +01:00

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Can't type tilde (~) in text editing mode - Blender enters fly/walk navigation immediately #82492