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

Non-US keyboard layout issues (Windows 7 SDL 1.2) #52

Open
malignantmanor opened this issue Jan 11, 2016 · 7 comments
Open

Non-US keyboard layout issues (Windows 7 SDL 1.2) #52

malignantmanor opened this issue Jan 11, 2016 · 7 comments
Labels

Comments

@malignantmanor
Copy link
Contributor

There is a bug report on the forum posted by kristo saying that the engine is using the US layout for keys instead of the German layout his keyboard uses. The "y" and "z" key are switched. This applies to casting spells by letter. I haven't gotten a reply about whether it affects npc conversations.

This was working for him in a 16, July 2014 build from Kirben in Windows 7. This bug is occurring in the current snapshot which also uses SDL 1.2.15. I couldn't see where the code changed that could have affected this. SDL 2 worked for him..

@malignantmanor malignantmanor changed the title Non-US keyboard layout issues Non-US keyboard layout issues (SDL 1.2) Jan 12, 2016
@DominusExult
Copy link
Member

Really odd. The OS X version works fine, the Windows snapshot works fine via Wine but in my VM with Windows 7 the keyboard behaves wrong... Very very strange...

@malignantmanor malignantmanor changed the title Non-US keyboard layout issues (SDL 1.2) Non-US keyboard layout issues (Windows 7 SDL 1.2) Jan 13, 2016
@DominusExult
Copy link
Member

As I have nothing set up to compile for Windows I can't tell for sure, but c35af1d looks like it could be the problem or hint to the problem...

@nickbe
Copy link

nickbe commented Aug 20, 2017

This worked some while ago with an SDL 1.2 build. But I'm back with the same error now.
Keys are switched. I thought this has aleady been fixed?

@nickbe
Copy link

nickbe commented Sep 22, 2017

Has this already been fixed in the latest builds?

@malignantmanor
Copy link
Contributor Author

I don't think it has. I'll try to contact Eric about fixing it.

@nickbe
Copy link

nickbe commented Sep 26, 2017

Thanks 😄

@nickbe
Copy link

nickbe commented Jun 6, 2020

Any news regarding this problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants