Caps Lock issues under Wine

[mark_k]

Hi,

Is anyone else seeing problems with Caps Lock when running WinUAE under Wine?

Boot with no startup-sequence, then keep pressing letter keys, occasionally pressing Caps Lock. The results I get are pretty messed-up running under Wine, with the case of the letters not reflecting the caps lock state.

Testing in a Windows XP VM things were mostly okay, though I did get some results like this when pressing Caps Lock once (while holding down Y obviously): yyyyyyyyyYYyYYYYYYYYYYY
Does that happen on a real Amiga?

[Minuous]

Originally Posted by mark_k

Hi,

Is anyone else seeing problems with Caps Lock when running WinUAE under Wine?

Boot with no startup-sequence, then keep pressing letter keys, occasionally pressing Caps Lock. The results I get are pretty messed-up running under Wine, with the case of the letters not reflecting the caps lock state.

Testing in a Windows XP VM things were mostly okay, though I did get some results like this when pressing Caps Lock once (while holding down Y obviously): yyyyyyyyyYYyYYYYYYYYYYY
Does that happen on a real Amiga?

Well, I can confirm there a known issue that the Caps Lock indicator on the keyboard doesn't reflect the Caps Lock state as perceived by the emulator. This happens on various flavours of Windows and isn't a WINE-related issue.

[mark_k]

I don't think that's the issue I'm seeing. When I run WinUAE under Wine, typing various keys while pressing Caps Lock sometimes can result in a string like this:

[caps lock on] hGFhGFhGFhGFhGFhGF [caps lock off] hgfhgfhgfhgf [caps lock on] hGFhGFhgFhGFhGF

Something's going wrong somewhere, but I don't know whether it's with Wine or the window manager, or something else. I'm testing with Lubuntu 11.10 here which uses the Openbox window manager. So I'd like to know whether anyone else is seeing the same issue, and if so which Linux distribution and window manager they are using.

[Toni Wilen]

Does Wine support raw input? WinUAE by default uses raw input for everything now unless it is not supported = fallback to old DirectInput.

[gilgamesh]

I remember having quirks with caps under wine. But I got the feeling that the behaviour was not random. (Turning caps lock off exclusively via left shift or something.)

The problems with the control mask are a more pressing issue for wine users. Once you press F12, you can only restart the machine. But this is OT of course.

[Toni Wilen]

I forgot, obviously raw input is not supported because F12 getting stuck can't happen in rawinput code path.

[Toni Wilen]

There appears to be separate wine rawinput patch (search "wine rawinput")

Changelog includes:

"Also I need to note the lack of applications that make extensive use of the raw input API. There are just a few games and they are convenient with just the mouse movement data"

I think winuae would be good test case. It uses all rawinput features, mouse, keyboard and USB HID devices. (including multiple mice and keyboards at the same time)

[Toni Wilen]

It seems wine 1.5.13 includes official rawinput support. In theory it should fix all wine winuae keyboard problems.

[mark_k]

In theory maybe, in practice no.

Testing with Wine 1.5.14 there's no change; the caps lock and reappearing settings window problems are still there. It looks like Wine's rawinput support isn't too great yet.

Part of the output on running winuae.exe -log (the 2nd line is printed by Wine):

RawInput enumeration..
fixme:win:GetRawInputDeviceList (pRawInputDeviceList=(nil), puiNumDevices=0x3f0f88c, cbSize=8) stub!
RAWINPUT: found 0 devices

[Toni Wilen]

Right, so Wine finally supports listening for rawinput events but it does not allow to enumerate rawinput devices. WinUAE needs it to detect from which device events come from, no devices detected -> fallback to DirectInput which has different issues in Wine..

I guess games that use rawinput don't need to care about it.

[Toni Wilen]

GetRawInputDeviceList is now marked as implemented in 1.5.16.

[mark_k]

I tested WinUAE 2.4.1 with Wine 1.5.16. Because WinUAE now defaults to using raw input, the caps lock issue is "fixed". Even better, the old reappearing settings window problem doesn't show up either! So WinUAE is now much more usable under Wine.

(I wrote fixed in quotes, because both bugs are still present in Wine; they show up if you run WinUAE with -norawinput option.)