-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not use keycodes file (yet?) #34
Comments
Even in US keyboard, when I specified keycode file in preference file, the guest OS crashed if I press any key. It complains missing vendor 'cocoa'
|
When I have the keycodes file specified (The Dutch keyboard is a QWERTY keyboard, much like the US QWERTY keyboard, but some characters, like ` and ~, are at different keys. I expect more problems with keyboards that are very different, like the French AZERTY keyboard.) |
In Mac and Linux, I built BII with autotools. |
@rickyzhang82 and @RonaldPR , can you post copies of the key-codes file(s) that you are trying to use? |
The keycodes file here attached (zipped). You may find the file with different names, but with identical content. However, as shown in Terminal output, your builds do not know some BasiliskII prefs settings, among which the ones for the keycodes: Basilisk II V1.0 by Christian Bauer et al. In the prefs file the use of the keycodes file is configured like this: keycodes true |
Build configure in Mac OS X
Warning
|
keycode link for Linux All my case is under English locale and US keyboard. |
I made a fork of David Ludwig macemu to add again keycode files in basilisk SDL2. Work on my French MacBook. |
@jvernet How about you send a PR to David's repo? |
The present releases do not (yet?) use the keycodes file, which makes use with non-US keyboard layouts difficult.
The text was updated successfully, but these errors were encountered: