[Bug 10643] WinUAE settings window reappears after being dismissed

wine-bugs at winehq.org wine-bugs at winehq.org
Sun Jun 12 08:56:01 CDT 2011


--- Comment #15 from Mark K <markk at clara.co.uk> 2011-06-12 08:56:00 CDT ---
WinUAE 2.1.0 (the last version for which -rawkeyboard works around this Wine
bug), as well and the most recent version 2.3.2 show 0 rawinput devices in the
"winuaebootlog.txt" file.

For WinUAE 2.2.0 and later, "-rawkeyboard" is now the default.

I noticed when testing WinUAE 2.3.2 under Wine 1.3.22, if I tap F12 very
briefly, the settings window does not reappear when dismissed. If I press F12
normally the settings window does reappear. Perhaps that behaviour depends on
PC speed? If F12 is pressed for a very short time on a slower PC, the key might
be released before the settings window is opened, which could avoid the

I have attached an archive containing WinUAE 2.1.0 boot logs with and without
the -rawkeyboard option. There are also some Wine logs. I created those using a
command like this:
WINEDEBUG=+key,+keyboard wine winuae.exe
then starting emulation, pressing F12 to bring up the settings window (if
necessary clicking in the main window and pressing F12 again), then quitting.
Try "diff"ing the files winuae2100_key_keyboard_log.txt and
winuae2100_-rawkeyboard_key_keyboard_log.txt to see how the keyboard is
accessed differently when -rawkeyboard is used.

Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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