Page MenuHome

macOS ALT/OPTION + E bug
Open, Needs Triage by DeveloperPublic

Description

System Information
Operating system: macOS High Sierra version: 10.13.6 (Macbook Pro 2015)
Graphics card: Intel Iris Graphics 6100

Blender Version
Broken: blender-2.80-6fd11a21f5c5-OSX-10.9-x86_64 (2018.3.11)

Short description of error
The first keystroke when entering anything (number, letter, or special character) in any number field after doing "Extrude Only Vertices and Move" via ALT/OPTION + E extrude (vertex, edge, or face) results in blender registering it as an apostrophe instead. Does not happen when doing an E extrude, scaling, moving, CTRL+B bevel, or rotating.

Exact steps for others to reproduce the error

  1. Open up most recent Blender 2.80 Beta build.
  2. Go into edit mode then extrude a vertex, edge, or face via the "Extrude Only Vertices and Move" ALT/OPTION+E method.
  3. Enter a letter, number, or special character in any number field. This is where the bug occurs. Instead of the intended letter, number, or special character appearing, an apostrophe appears. In the provided video I am attempting to enter the number 1, but instead an apostrophe appears. I have to delete and then re-enter a number. Only occurs during the first time you enter a number after you do an ALT/OPTION+E extrude.

Example:

Details

Type
Bug

Event Timeline

I cannot reproduce this here on macOS 10.14 either.

But to me, the steps needed to reproduce this aren't clearly enough spelled out.

EXACTLY what are you doing that makes the apostrophe appear? We cannot see your keyboard or mouse input here.

William Reynish (billreynish) triaged this task as Needs Information from User priority.Mar 11 2019, 7:03 PM

I thought I was pretty clear and concise when I said use the ALT + E extrude method then attempt to enter a number in the number field in the edit window that pops up in the bottom left corner. Added further instructions to clarify any confusion.

I've also updated the example video, this time it has a screen cast add-on that shows what I'm pressing/clicking. (However, it seems the add-on doesn't capture when I enter a number in the number field within the edit window.) I am attempting to enter a 1, but when I do Blender registers it as an apostrophe. I double checked to see if it might be my keyboard or any other number key giving me an issue, but it is not. It also doesn't matter if the number is entered through the number keys above qwerty or the numpad.

Try doing File > Load Factory Settings and test again.

Vlitz (Vlitz) added a comment.EditedMar 11 2019, 11:57 PM

Tested and the bug still persists. I took a look at the terminal output this time to see if it might shed any light. I am getting this line ui_do_but_textedit: utf8 char '´' the moment I try to enter the number for the first time. Not sure what it means. I've attached the terminal output.

You seem to be using some kind of addon. Try and disable the addon and re-test.

I've tested again disabling all addons and using the latest fresh installation (though, I thought Load Factory Setting achieved that). The bug is still there. I did further testing and discovered the apostrophe bug occurs when you enter anything (letters, numbers, or special characters). For example, blender registers holding Shift + 1 to enter an exclamation point as an apostrophe.

Ok, so this has nothing to do with extruding then? Can you change the title of the bug report? Thanks.

What kind of keyboard are you using, and what is the system language?

Vlitz (Vlitz) added a comment.EditedMar 12 2019, 4:46 PM

It only occurs within the number field of the edit window from ALT + E specifically. Scaling, moving, extruding using E, and CTRL + B bevel seem to not have the bug. That's why I included the ALT + E extrude in the title. But I will rename it so it reflects the bug more clearly.

I use U.S. English, and I use a mechanical keyboard from Das Keyboard. However, I've tested the bug using the laptop's keyboard which yielded the same result.

To further investigate out of curiosity, I've tested to see if it occurs in Blender 2.79. Can't replicate the bug there.

Vlitz (Vlitz) renamed this task from Alt + E extrude apostrophe bug to Blender registering the first keystroke as an apostrophe in the numberfield of the edit window (specifically after using ALT+E).
Sebastian Parborg (zeddb) raised the priority of this task from Needs Information from User to Needs Triage by Developer.Mar 12 2019, 5:06 PM

Well, I still cannot reproduce the issue here. Tested on several macOS systems here.

Yes, this bug occurs when "Extrude Only Vertices and Move" executed via Alt+E, but not via menu or search.

Moreover, it's not relative to Extrude,
it's a kind of macOS feature with Option-E.

https://slcr.wsu.edu/help-pages/keyboards-osx/

macOS feature with Option-E.

This makes a whole lot more sense. Thank you for pointing it out. Renaming task to reflect the bug more accurately.

Ok, well, in that case I'm not sure there's much we can do. If your OS version or language overrides Option-E, you'll have to turn that off in the OS.

Vlitz (Vlitz) renamed this task from Blender registering the first keystroke as an apostrophe in the numberfield of the edit window (specifically after using ALT+E) to macOS ALT/OPTION + E bug.Mar 13 2019, 3:02 PM
Vlitz (Vlitz) added a comment.EditedMar 13 2019, 3:11 PM

If it was the OS version or language overriding OPTION-E, then shouldn't this bug be replicated in Blender 2.79? As I've previously noted, I cannot replicate it in 2.79--OPTION+E behaves the way it should. I've only run across this issue within the latest 2.80 beta versions.
I've also checked the language/keyboard input settings and they are all at the default settings. No settings have been tampered with or changed. At this point, I'm not sure what other information I can provide that will shed light to this bug.

EDIT: After further investigation, it CAN be produced in 2.79. An oversight on my end.

Well, I certainly cannot reproduce the issue here on Mac. I am using 10.14.2. Perhaps it's an issue with High Sierra?

I agree that it most likely is an issue with High Sierra. I went back to 2.79 to make sure I did exactly what I was doing in 2.80 and was able to replicate it (can never be too sure). Previously, I pressed F6 to bring up the edit window after doing ALT+E which subsequently was the first keystroke (an oversight on my end). This time I made sure to just click on any number field first before pressing anything and I was able to replicate the bug. This plus your testing on 10.14.2 leads me to think the bug is contained within High Sierra.

Ok. Archiving for now then. You can respond when you have updated to 10.14 and re-tested.

This function works in this way: for example, you press Option-E and then immediately A, so "a" will be converted in the "á".
In other applications, if after Option-E you click somewhere it reset this function.
Blender "remembers" this, you can perform some action after Option-E and then when you try to enter the symbol it will convert.

@William Reynish (billreynish) Try also Alt-I (Delete Keyframe) then move the object using gizmo, and then try entering some value.

Vlitz (Vlitz) added a comment.EditedMar 13 2019, 4:21 PM

Blender "remembers" this, you can perform some action after Option-E and then when you try to enter the symbol it will convert.

Is there a way for Blender to not "remember" this or have it reset like in other applications? Or is it something completely out of the developers' hands?

You can respond when you have updated to 10.14 and re-tested.

Making users to update to the latest macOS seems a little...forceful. If it really is the only solution, then it is an acceptable quirk of using Blender on High Sierra. I only bring up this point because what if users' machines aren't optimized for 10.14 or have software that will break with the update to 10.14? I think other avenues should be explored in addressing this bug before dismissing this in such a way.

I would appreciate a clear response saying updating to 10.14 is the only solution to this bug.

The updating won't help you, I'm using 10.14.3.
You can remap Alt-E to Cmd-E, if it's critical to you.

This comment was removed by Vlitz (Vlitz).

I still cannot reproduce this on any of the Macs I have access to here. Can you turn it off in System Preferences?

https://en.wikipedia.org/wiki/Diacritic#Generation_with_computers

It seems you need to have some international keyboard, there are no settings in System Preferences, it depends on keyboard layout.

But, again, this problem is not present in other programs.

To those who have this issue: Which system keyboard language do you have set in System Preferences? Can you test with other languages?

It probably also depends on your system language, not just the keyboard layout.
If you have "English (US)" language, the keyboard will not present "dead key" behavior, because they are not used in english.

I also reproduced the same bug on Windows with "US International" layout. In my case, the "dead keys" is grave accent, Shift+~, Shift+6.

So it seems to me (although I don't know how it works) we need to reset the "dead key state" when performing operation via hotkey.

Since it is not MacOS specific, it may be necessary to change the title of this task.