Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with non English keyboards #21604

Open
DemAvalon opened this issue Aug 10, 2017 · 4 comments
Open

Problem with non English keyboards #21604

DemAvalon opened this issue Aug 10, 2017 · 4 comments
Labels
Accessibility Issues regarding accessibility <Bug> This needs to be fixed (P5 - Long-term) Long-term WIP, may stay on the list for a while.

Comments

@DemAvalon
Copy link
Contributor

When pressing keys such as ^ ~ ´ ` ¨ it will require two key presses from the key to use a function mapped to these keys (^ is default for control vehicle and ~ is the default for white list enemy)

AdonaiJr: My guess is that on some languages, like Portuguese (it uses some chars like ô, ê), the keyboard/language in the system is setup as follows:

As soon as you press the key ^, it doesn't display anything, it "applies" the ^ to the next key you press, usually a vowel.

I think the previous way Cataclysm identified a key was through a "pure" keypress. Something changed and now it identifies like a "return from the system" for that char, ^.

If you press ^ and then -space-, it will work too, because internally the ^ char will only really "appear" after being applied to something.

My guess is that they changed something in the code that now captures keypress differently.

Thanks to AdonaiJr for properly wording the issue.

@DemAvalon DemAvalon changed the title Problem with non english keyboards Problem with non English keyboards Aug 10, 2017
@Night-Pryanik Night-Pryanik added the Accessibility Issues regarding accessibility label Aug 11, 2017
@BevapDin
Copy link
Contributor

My guess is that they changed something in the code that now captures keypress differently.

Would be really helpful to know when this change happened (which most recent version did work).

@DemAvalon
Copy link
Contributor Author

I don't know exactly which version made the change (I stopped playing for 8-9 months, then updated and noticed the change) the earlier version I noticed this was on 6537, sorry I can't give more information.

@exuvo
Copy link
Contributor

exuvo commented Apr 28, 2018

I just got back into playing Cataclysm and tried the latest version and got this problem. I usually have the crafting menu on ^ so it is really irritating having to press it twice.
The old version I used to play dated 2017-05-10 0.C-22241-g836610010b does not have this issue.

So between 2017-05-10 and 2017-08-11 is where we should be looking.

-Edit-
Maybe my install was from an older file as I just went through the changelog between those dates and read every line but found nothing relevant.

@stale
Copy link

stale bot commented Aug 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. Please do not 'bump' or comment on this issue unless you are actively working on it. Stale issues, and stale issues that are closed are still considered.

@stale stale bot added the stale Closed for lack of activity, but still valid. label Aug 20, 2019
@kevingranade kevingranade added the <Bug> This needs to be fixed label Aug 21, 2019
@stale stale bot removed the stale Closed for lack of activity, but still valid. label Aug 21, 2019
@esotericist esotericist added this to To do in User Experience Oct 29, 2019
@esotericist esotericist moved this from To do to Accessibility issues in User Experience Oct 29, 2019
@ZhilkinSerg ZhilkinSerg added the (P5 - Long-term) Long-term WIP, may stay on the list for a while. label Nov 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility Issues regarding accessibility <Bug> This needs to be fixed (P5 - Long-term) Long-term WIP, may stay on the list for a while.
Projects
User Experience
  
Accessibility issues
Development

No branches or pull requests

6 participants