[Bug 40256] New: user32:input fails on non-qwerty keyboards

wine-bugs at winehq.org wine-bugs at winehq.org
Sun Mar 6 14:15:53 CST 2016


https://bugs.winehq.org/show_bug.cgi?id=40256

            Bug ID: 40256
           Summary: user32:input fails on non-qwerty keyboards
           Product: Wine
           Version: 1.9.3
          Hardware: x86
                OS: Windows
            Status: NEW
          Severity: normal
          Priority: P2
         Component: user32
          Assignee: wine-bugs at winehq.org
          Reporter: fgouget at codeweavers.com

Since the commit below, user32:input has the following failures on azerty
keyboards:

input.c:1688: Test failed: 12: got 1 expected 0
input.c:1690: Test failed: 12: got L"\001d" expected L""
input.c:1688: Test failed: 17: got 1 expected 0
input.c:1690: Test failed: 17: got L"\001c" expected L""
input.c:1688: Test failed: 25: got 1 expected 0
input.c:1690: Test failed: 25: got L"\001c" expected L""
input.c:1688: Test failed: 30: got 0 expected 1
input.c:1688: Test failed: 31: got 0 expected 1
input.c:1688: Test failed: 32: got 0 expected 1
input.c:1690: Test failed: 33: got L"\001b" expected L"\001e"
input.c:1688: Test failed: 34: got 0 expected 1

Unfortunately we don't have TestBot VMs with non-qwerty keyboards so far but
this can be seen on the fg-eeepc-xp and fg-acer64-* Windows test results.

winspool's dr-w8-E1-1200-x64 has slightly different test failures which is most
likely because it has a qwertz keyboard (based on the German locale):
https://test.winehq.org/data/0806b06f2ba7a690661d6ae417270bdbc7370953/win8_dr-w8-E1-1200-x64_1/user32:input.html

input.c:1688: Test failed: 10: got 1 expected 0
input.c:1688: Test failed: 11: got 1 expected 0
input.c:1690: Test failed: 11: got L"\001c" expected L""
input.c:1688: Test failed: 18: got 1 expected 0
input.c:1690: Test failed: 18: got L"\001d" expected L""
input.c:1690: Test failed: 29: got L"\0011" expected L""
input.c:1688: Test failed: 30: got 0 expected 1
input.c:1688: Test failed: 31: got 0 expected 1
input.c:1688: Test failed: 32: got 0 expected 1
input.c:1688: Test failed: 33: got 0 expected 1

And gang65 at poczta.onet.pl's win7sp1 machine has yet another set of failures,
probably due to the presence of a Polish keyboard:
https://test.winehq.org/data/b190a72bfe53a41a83ae55d75de8327c24512bee/win7_win7sp1/user32:input.html

input.c:1688: Test failed: 10: got 1 expected 0
input.c:1688: Test failed: 28: got 1 expected 0
input.c:1690: Test failed: 28: got L"\001f" expected L""
input.c:1690: Test failed: 29: got L"\0016" expected L""
input.c:1690: Test failed: 31: got L"\0011" expected L"\001c"
input.c:1688: Test failed: 33: got 0 expected 1
input.c:1688: Test failed: 34: got 0 expected 1

mshtml:script results on test.winehq.org:
https://test.winehq.org/data/tests/user32:input.html

commit 10556c25e468768d1422e872f16dbc1ae85ef968
Author: Huw Davies <huw at codeweavers.com>
Date:   Thu May 28 11:35:05 2015 +0100

    winex11: Fix ctrl-<symbol> to generate codes below 0x20 where necessary.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list