[Bug 11607] New: Blood 2: The Chosen keyboard repeat problem

http://bugs.winehq.org/show_bug.cgi?id=11607

Summary: Blood 2: The Chosen keyboard repeat problem
           Product: Wine
           Version: 0.9.55.
          Platform: All
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Hi there,

I'm filing another Blood 2 bug. This one is input related, more precisely about
keyboard input. I know that the Blood 2 informations on the net mentioned the
support for DirectInput devices, but I'm not sure this is a dinput bug. So I'm
leaving this to unknown for now.

To the problem:
I installed Blood 2 through wine and did no patching (version is still 1.0).
Also the copy protection was not removed, the executable should be clean.

Starting the game and entering the configuration menu I noticed it was very
hard to setup the keys I wanted to use in the game (like moving forward,
backward, etc.)

When running Blood 2 natively you select a action in the menu you want to map.
You press ENTER and the game engine waits for you to press another key, which
it uses for mapping.

Now when running wine I had to be REALLY quick when pressing the mapkey. Like
some milliseconds later, it was really no fun to config the game. When I wasn't
quick enough for an action the ENTER key itself is mapped.

Now the interesting part. When not releasing the ENTER key after pressing it,
and then pressing the mapkey, the process works.

I suspect that the ENTER key generates two events for the game. Pressing and
releasing, and the game interprets both events as seperate key presses, so
ENTER gots mapped to everything (because the engine thinks it's pressed twice).

So either this is X related or a bug in the wine's keyb implementation.

Thanks,
Tobias