macOS ALT/OPTION + E bug #62456

Closed
opened 2019-03-11 16:54:49 +01:00 by Vlitz · 38 comments

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
Thefirst 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+Emethod.
  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:
bug.mov

**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:** [bug.mov](https://archive.blender.org/developer/F6804528/bug.mov)
Author

Added subscriber: @Vlitz

Added subscriber: @Vlitz

Added subscribers: @WilliamReynish, @ZedDB

Added subscribers: @WilliamReynish, @ZedDB

I can not reproduce this. It works fine for me.
@WilliamReynish can you reproduce this?

I can not reproduce this. It works fine for me. @WilliamReynish can you reproduce this?

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.

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.
Author

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 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.
Author

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.

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.

Try doing File > Load Factory Settings and test again.
Author

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.
bug

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. [bug](https://archive.blender.org/developer/F6805802/bug)

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

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

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.

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?

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?
Author

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.

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 changed title 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) 2019-03-12 16:50:59 +01:00

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

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

Added subscriber: @jenkm

Added subscriber: @jenkm

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

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/

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/
Author

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.

> 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.

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 changed title 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 2019-03-13 15:02:52 +01:00
Author

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.

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?

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

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.

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.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
William Reynish self-assigned this 2019-03-13 15:47:58 +01:00

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

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.

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.

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

@WilliamReynish Try also **Alt-I** (Delete Keyframe) then move the object using gizmo, and then try entering some value.
Author

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.

> 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.

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.
Author

This comment was removed by @Vlitz

*This comment was removed by @Vlitz*

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

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.

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?

To those who have this issue: Which system keyboard language do you have set in System Preferences? Can you test with other languages?
@WilliamReynish How does your layout look? ![ABC.png](https://archive.blender.org/developer/F6821177/ABC.png) https://en.wikipedia.org/wiki/Dead_key https://stackoverflow.com/questions/33203020/get-the-char-accent-in-nsevent https://docs.microsoft.com/ru-ru/windows/desktop/inputdev/about-keyboard-input#dead-character-messages

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'

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.

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.

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

Added subscriber: @AdamPreisler

Added subscriber: @AdamPreisler

I think the best solution is to use US or other international keyboard layout when using blender. It solves lots of issues.

Otherwise in Blender while using localized keyboard layouts (there's a lot) when keys are pressed they would be remapped from all the possible keyboard languages inputs onto the same keys that occupy the space on the US layout to solve this bug

Might be too much effort though, possibly better to learn the shortcut to change to US.

I myself use Czech and US layout so I need to switch between them. Czech is mainly used for typing .. in Czech^..^

It is also odd that Bill can't reproduce this on any of his Macs I guess he definitely uses international keyboard layout.

@WilliamReynish consider archiving this?

I think the best solution is to use US or other international keyboard layout when using blender. It solves lots of issues. **Otherwise in Blender while using localized keyboard layouts (there's a lot) when keys are pressed they would be remapped from all the possible keyboard languages inputs onto the same keys that occupy the space on the US layout to solve this bug** Might be too much effort though, possibly better to learn the shortcut to change to US. I myself use Czech and US layout so I need to switch between them. Czech is mainly used for typing .. in Czech^..^ It is also odd that Bill can't reproduce this on any of his Macs I guess he definitely uses international keyboard layout. @WilliamReynish consider archiving this?

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#62456
No description provided.