Dead Keys failing (accented letters, double strokes) #84800

New Issue

Christos · 2021-01-17T13:02:11+01:00

Christos commented

2021-01-17 13:02:11 +01:00

System Information
Operating system: Windows 10 X64 Enterprise
Graphics card: Nvidia RTX 2070 MaxQ

Blender Version
Broken: 2.73, 2.91.0
Worked: Never

Short description of error
In a text editor window, using Unicode national characters (Greek in my case), there are accented vowels that register with two keys from the keyboard (eg: ά, έ, ό … etc).
If I type the 2 key sequence fast, the accent is missed, slower works. Is this a delay that can be set in Blender, or an interpreter lag that cannot be adjusted?
Actually I think it happens everywhere (not only text editor), but it’s especially nagging problem in a text window, where I may type whole paragraphs and almost each word has an accent.

Exact steps for others to reproduce the error

In the text editor, press and hold the dead key
without releasing the dead key, press the key to be transformed. (this will fail)

If you release the dead key before pressing the key to be changed, it will work normally.

**System Information** Operating system: Windows 10 X64 Enterprise Graphics card: Nvidia RTX 2070 MaxQ **Blender Version** Broken: 2.73, 2.91.0 Worked: Never **Short description of error** In a text editor window, using Unicode national characters (Greek in my case), there are accented vowels that register with two keys from the keyboard (eg: ά, έ, ό … etc). If I type the 2 key sequence fast, the accent is missed, slower works. Is this a delay that can be set in Blender, or an interpreter lag that cannot be adjusted? Actually I think it happens everywhere (not only text editor), but it’s especially nagging problem in a text window, where I may type whole paragraphs and almost each word has an accent. **Exact steps for others to reproduce the error** - In the text editor, press and hold the dead key - without releasing the dead key, press the key to be transformed. (this will fail) If you release the dead key before pressing the key to be changed, it will work normally.

Christos commented

2021-01-17 13:02:11 +01:00

Added subscriber: @xs

blender-admin commented

2021-01-17 13:02:11 +01:00

#104185 was marked as duplicate of this issue

Christos commented

2021-01-18 13:04:31 +01:00

It was suggested that possibly this is what happens:

a press followed by a press is different from a press followed by release. When you’re typing quickly, you might be pressing the next key before releasing the previous one, and this can (and does) lead to an apparent misinterpretation of events.

My question then is Blender different than the way most software handles keyboard input? I can imagine combining an alphanumeric key with certain special keys likes shift, alt, control or function keys, having meaning, it is a common interpretation for all software. But combining simple letter keys, must be interpreted differently by other software, since I don’t have the same problem. How is that uniquely useful to Blender functionality (to wait for key release in alphanumeric keys)? And can I turn it off?
Should it be off by default, relying on key press alone (not release) for letter keys to behave consistently as other software?

It was suggested that possibly this is what happens: > a press followed by a press is different from a press followed by release. When you’re typing quickly, you might be pressing the next key before releasing the previous one, and this can (and does) lead to an apparent misinterpretation of events. My question then is Blender different than the way most software handles keyboard input? I can imagine combining an alphanumeric key with certain special keys likes shift, alt, control or function keys, having meaning, it is a common interpretation for all software. But combining simple letter keys, must be interpreted differently by other software, since I don’t have the same problem. How is that uniquely useful to Blender functionality (to wait for key release in alphanumeric keys)? And can I turn it off? Should it be off by default, relying on key press alone (not release) for letter keys to behave consistently as other software?

Long Hoang commented

2021-05-11 03:31:37 +02:00

Added subscriber: @htlcnn

Long Hoang commented

2021-05-26 16:57:06 +02:00

Or just disable hot keys capture when you're typing in a text input?

Philipp Oeser commented

2022-02-21 10:22:34 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-02-21 10:22:34 +01:00

note #95410 (Regression: Blender text editor lost support for dead keys) is related (so it is harder to check on linux now)

Germano Cavalcante changed title from ~~Unicode haracters in text editor, problem with accented letters, double strokes~~ to Dead Keys failing (accented letters, double strokes)

2022-02-22 14:41:00 +01:00

Germano Cavalcante commented

2022-02-22 14:43:41 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2022-02-22 14:43:41 +01:00

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

Germano Cavalcante commented

2022-02-22 14:43:41 +01:00

I can confirm on windows.
It's not the same problem as #95410 (Regression: Blender text editor lost support for dead keys) as this one is quite old.

I can confirm on windows. It's not the same problem as #95410 (Regression: Blender text editor lost support for dead keys) as this one is quite old.

Pratik Borhade commented

2023-01-30 02:27:45 +01:00

Added subscriber: @Gabriel-Solis

Christos commented

2023-01-30 07:15:09 +01:00

Exact steps for others to reproduce the error
In the text editor, press and hold the dead key
without releasing the dead key, press the key to be transformed. (this will fail)
If you release the dead key before pressing the key to be changed, it will work normally.

Somewhere along the way my original report of this problem has changed, the above DOES NOT reproduce the error I was reporting (though it may be something else, reported or not)
Accented Greek is a key combination in sequence: modifier (accent) first, followed by letter key.
My problem is it fails when I press the modifier key, release and then press the letter to be transformed with the accent, quickly, or so I think... , but can't be sure when I type quickly. I'm sure the accents work fine in other software the way I type, even fast, but, I did notice that in the word processor, for example, it works either way: still holding the modifier OR released.
I guess Blender is different? Could it not be the same as most all other software? in this way it interprets accented letter sequences?

> Exact steps for others to reproduce the error > > In the text editor, press and hold the dead key > without releasing the dead key, press the key to be transformed. (this will fail) > > If you release the dead key before pressing the key to be changed, it will work normally. Somewhere along the way my original report of this problem has changed, the above DOES NOT reproduce the error I was reporting (though it may be something else, reported or not) Accented Greek is a key combination in sequence: modifier (accent) first, followed by letter key. My problem is it fails when I press the modifier key, release and then press the letter to be transformed with the accent, quickly, or so I think... , but can't be sure when I type quickly. I'm sure the accents work fine in other software the way I type, even fast, but, I did notice that in the word processor, for example, it works either way: still holding the modifier OR released. I guess Blender is different? Could it not be the same as most all other software? in this way it interprets accented letter sequences?

G. Solis commented

2023-01-30 20:08:05 +01:00

Added subscriber: @PratikPB2123

G. Solis commented

2023-01-30 20:08:05 +01:00

@PratikPB2123

The issue I'd opened (#104185) just got merged into this one, but they don't appear to be the same at all.

Mine has something to do with a "failed keycode lookup", and no bearing on the timing between the two keystrokes: it fails regardless.
Furthermore, I'm fairly sure mine is Linux-specific.

As far as I can tell, the issue I've opened should be merged with #95410.

@PratikPB2123 The issue I'd opened (#104185) just got merged into this one, but they don't appear to be the same at all. Mine has something to do with a "failed keycode lookup", and no bearing on the timing between the two keystrokes: it fails regardless. Furthermore, I'm fairly sure mine is Linux-specific. As far as I can tell, the issue I've opened should be merged with #95410.

Pratik Borhade commented

2023-01-31 02:42:52 +01:00

Right, I merged into the wrong report. Sorry for the noise

G. Solis commented

2023-01-31 02:49:01 +01:00

Not at all, you're doing god's work mate. Much appreciated

Harley Acheson commented

2023-01-31 03:29:18 +01:00

Added subscriber: @Harley

Harley Acheson commented

2023-01-31 03:29:18 +01:00

In the text editor, press and hold the dead key
without releasing the dead key, press the key to be transformed. (this will fail)

As far as I have ever known this is how it is supposed to work. Dead keys are not modifiers, like Shift Ctrl, Alt, etc. Modifiers change the behavior of other keys while they are depressed. But dead keys are dead, as in they do nothing when pressed and released, but the next key is altered.

While I have the US International Keyboard enabled I have a few dead keys, like ` and ^ and ''. Pressing one and then a key that can take such an accent will result in that character. So backtick then ''a'' gives me ''à"", and backtick then e gives me è

But I can demonstrate that the backtick is a dead key and not a modifier. In any application. Following is tested in Notepad

If I hold down the SHIFT key, and keep it depressed, I can type ae and get AE.

However if I hold down backtick, and keep it depressed, and type ae I get àe, NOT àè

Dead keys just aren't designed to work as modifiers.

I'm not sure how that is even possible. With the dead keys you can get that key if your press it twice. So backtick then backtick gives me a backtick. But deadkeys are also repeatable, while modifiers are not. As in you can hold down a shift key forever and it will do not harm. But hold down a deadkey for more than about half a second and you will get a repeating entry of ````````````````````````````````

> In the text editor, press and hold the dead key > without releasing the dead key, press the key to be transformed. (this will fail) As far as I have ever known this is how it is supposed to work. Dead keys are **not** modifiers, like Shift Ctrl, Alt, etc. Modifiers change the behavior of other keys while they are depressed. But dead keys are **dead**, as in they do nothing when pressed and released, but the next key is altered. While I have the US International Keyboard enabled I have a few dead keys, like ` and ^ and ''. Pressing one and then a key that can take such an accent will result in that character. So backtick then ''a'' gives me ''à"", and backtick then e gives me è But I can demonstrate that the backtick is a dead key and not a modifier. In any application. Following is tested in Notepad If I hold down the SHIFT key, and keep it depressed, I can type ae and get AE. However if I hold down backtick, and keep it depressed, and type ae I get àe, NOT àè Dead keys just aren't designed to work as modifiers. I'm not sure how that is even possible. With the dead keys you can get that key if your press it twice. So backtick then backtick gives me a backtick. But deadkeys are also repeatable, while modifiers are not. As in you can hold down a shift key forever and it will do not harm. But hold down a deadkey for more than about half a second and you will get a repeating entry of ````````````````````````````````

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Dead Keys failing (accented letters, double strokes) #84800