equal
deleted
inserted
replaced
1 #summary Solutions for fixing bug 240 (frontend displays wrong key name) |
1 #summary Solutions for fixing bug 240 (frontend displays wrong key name) |
2 |
2 |
3 This wiki page is for documenting and analyzing possible solutions for [https://issues.hedgewars.org/show_bug.cgi?id=240 bug 240] that have been discussed before. |
3 This wiki page is for documenting and analyzing possible solutions for [https://issues.hedgewars.org/show_bug.cgi?id=240 bug 240] that have been discussed before. |
4 |
4 |
5 ## Criteria |
5 == Criteria == |
6 |
6 |
7 First, for a working solution, it should match these criteria: |
7 First, for a working solution, it should match these criteria: |
8 |
8 |
9 # They key you selected in frontend is the key that you actually need to push (so if it says “Z”, you must press the “Z” key in game; it must respect keyboard layout). This is the bug that was reported |
9 # They key you selected in frontend is the key that you actually need to push (so if it says “Z”, you must press the “Z” key in game; it must respect keyboard layout). This is the bug that was reported |
10 # The key that is displayed in frontend must match the key that is saved in config file |
10 # The key that is displayed in frontend must match the key that is saved in config file |
11 # (optional) Engine is able to convert the code to human-readable text. It's not a bug if it's not possible, however |
11 # (optional) Engine is able to convert the code to human-readable text. It's not a bug if it's not possible, however |
12 # Default key config works with MOST normal keyboards (100% perfect coverage not required as its unrealistic; owners of exotic keyboards are expected to reconfig) |
12 # Default key config works with MOST normal keyboards (100% perfect coverage not required as its unrealistic; owners of exotic keyboards are expected to reconfig) |
13 |
13 |
14 ## Possible solutions |
14 == Possible solutions == |
15 |
15 |
16 === A) Use keycode in frontend and config file, use scancode in engine (current broken approach) === |
16 === A) Use keycode in frontend and config file, use scancode in engine (current broken approach) === |
17 |
17 |
18 Criteria: |
18 Criteria: |
19 |
19 |