Brazilian Keyboard Layout: Can not connect different commands on Windows. #23685
Assignees
Labels
bug
Issue identified by VS Code Team member as probable bug
keybindings
VS Code keybinding issues
keyboard-layout
Keyboard layout issues
verified
Verification succeeded
windows
VS Code on Windows issues
Milestone
Comments
alexdima
added
keyboard-layout
alexdima
changed the title
|
There is one key in your gif that prints unknown and that is not mappable for you, the May I kindly ask that you press this key and hover over the input box as I do in the gif below. Here I am doing it for
|
|
@alexandrudima Be the gif in the VSCode for the two keys, first the
Here's the Chrome image:
|
|
Thank you @Tekbr
But it looks like there is high consensus that these two values should be used for Brazilian:
We need to add support for them both in https://github.com/Microsoft/node-native-keymap and in VS Code for them to work properly |
alexdima
added a commit
to microsoft/node-native-keymap
that referenced
this issue
May 11, 2017
alexdima
added a commit
that referenced
this issue
May 11, 2017
|
Thank you @alexandrudima . I look forward to updating VSCode-Insiders tomorrow. 🎉 😄 Thank you one more time. And congratulations to you and the whole team. 👏👏👏👏👏 |
|
@alexandrudima See the gif.
I think some details are missing. The same does not appear yet according to what I typed. That is with the key of my keyboard. Note: When you press [ or ] for the first time, two combinations occur. But when pressed for a second time the same appears a unique combination. |
|
@alexandrudima This is the result when I run: developer: Inspect key Mappings Click to expand |
|
The difference between the input box and the rendered key under the input box is ... confusing, but expected. The input box represents the keyCode and the rendered key under the input box represents the key label as it should appear on the keyboard ... From looking at your gif and correlating with the keybinding data:
.. etc This is very confusing, I agree, and perhaps we should always use the symbolic names inside the input box in such cases, such as The two keys looks very funny indeed, perhaps the widget thinks it goes into a chord. So I think the action for me here would be to use the symbolic names in the |
-- Sorry for the English, I used Google Translator -- @alexandrudima, I did not quite understand. But the ideal is if I pressed As for a problem I mentioned in the previous comment (clicking on Then do the steps according to the gif.
On the virtual keyboard the And yes, now I can set the keys. But look closely at this situation. Please tell me if this is a new issue. I may be expressing myself wrong, but in my view: - Before its correction: VSCode did not know and did not understand the Brazilian keyboard. What do I mean by that? (This may apply to other types of keyboard and not just the Brazilian) The default shortcut for Toogle Line Comment by default of VSCode according to the site is Does the key exist on my keyboard? Yes there is. Is she in a different place than the American keyboard? Yes, it's in a different place. What VSCode is doing: For me this is not right. What it should do: For when the key does not exist. What to do: (I do not know if the same does it)
How hard is that to fix? Do not know. But it's an important point yes. @alexandrudima Maybe it got a bit confusing. Let me know what you could understand or what you could not understand. |
|
I have documented in great detail the way keybindings work in VS Code at https://github.com/Microsoft/vscode/wiki/Keybindings#ecode-ekeycode-and-ekey (starting with the section labeled VS Code does not ship with keyboard layout specific default keybindings. This is something that you can upvote in #1240 The website shows the keybindings as they are on the US standard keyboard layout. Here is what is happening on Windows on your keyboard layout with the default keybinding for Toggle Line Comment:
Regarding the pressing of the |
|
Ok @alexandrudima . I think the biggest problem was recognizing the keys. So let's move on slowly. As for me pushing Now it shows I commented on both issues(#26945) because I was in doubt on which to track |
|
Extracted last comment to #27088 |
|
I tried to understand what needs to be verified, but I give up :) |
|
To verify, bring up the on screen keyboard on Windows with the Brazilian Portuguese keyboard layout. It should look something like this:
Then press the |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
-- Sorry for the English, I used Google Translator --
@alexandrudima As you suggested in the #22626
Steps to Reproduce:
1- Edit keybindings.json
2- Click Define Keybinding (Ctrl + K Ctrl + K)
3- Press Ctrl + ; on a Brazilian Keyboard
Expected:
Keys showed should be Ctrl + ;
Result:
Keys showed is Ctrl + /
Here a gif with the keys that are different in Brazilian keyboard.
Here is an example of a Brazilian keyboard. (The settings of the keyboards may vary depending on the notebook manufacturer or keyboard manufacturer).
Example of the keyboard I use.
Image of Wikipedia, where it shows that some keys can change position. Example: / in blue.
The text was updated successfully, but these errors were encountered: