2141d2fe3a
- This key code is inherited from BeOS, where it was used for the power key on Apple ADB keyboards - Since then, we have introduced a new system for "multimedia" keys, that uses HID key codes directly instead of defining our own mappings - The PS2 driver was using the HID keycode, but the USB driver was still using the BeOS defined one - Japanese keyboards, which have a few more keys than US and European ones, reused the same keycode for something else Since the power key does not need to be mapped by the keymap, move it out of the way by using the HID keycode (key codes larger than 0x7f cannot be mapped to UTF8 symbols). Remove all mentions of the use of 0x6b as a keycode for the power key, but add a note in the documentation that BeOS did this. To avoid further confusions, complete the documentation of extra keycodes, and remove some definitions from keyboard_mouse_driver.h that should have been in InterfaceDefs.h. While researching this, I also found that some keys specific to Korean keyboards were declared in the wrong place, as mapped codes instead of unmapped ones (checked that by looking at the HID driver, which emits these raw keycodes, and confirming that the mapped ones are not used in any keymaps. Also added a note about the mapping of the extra modifier keys in Japanese keyboards, which I think may be a problem since these map to invalid UTF-8 byte sequences, but this is what the existing keymap does, so leaving it as is for now until we can determine if this can be changed or if we have to keep it that way. Change-Id: I6a198a0840cba7739bdc78e0c65e5d8fd23956c9 Reviewed-on: https://review.haiku-os.org/c/haiku/+/8047 Tested-by: Commit checker robot <no-reply+buildbot@haiku-os.org> Reviewed-by: Adrien Destugues <pulkomandy@pulkomandy.tk> |
||
|---|---|---|
| 3rdparty | ||
| build | ||
| data | ||
| docs | ||
| headers | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| .gitreview | ||
| configure | ||
| Jamfile | ||
| Jamrules | ||
| License.md | ||
| ReadMe.Compiling.md | ||
| ReadMe.md | ||
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.