Feature #106
Finish InputManager/HID layer
| Status: | Closed | Start: | 03/04/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Eduard Burtescu |
% Done: | 100% |
|
| Category: | Kernel | Spent time: | - | |
| Target version: | Foster Post-Release Milestone #1 |
Description
The InputManager needs to take a shape in order to support mice and be ready for the GUI.
I also have in mind changes to the keyboard handling:- Either implement only keyDown and keyUp events and let TUI/GUI handle repeat.
- Either implement keyDown and keyUp events as above, but also a keyPress event, sent from the worker thread repeatedly, with extra support from TUI/GUI.
History
Updated by Matthew Iselin about 1 year ago
- Status changed from New to Assigned
- Assigned to set to Matthew Iselin
Updated by Matthew Iselin about 1 year ago
- Assigned to changed from Matthew Iselin to Eduard Burtescu
- % Done changed from 0 to 40
Created InputManager::keyDown and InputManager::keyUp. keyPress needs to be re-implemented for devices which don't do keyDown/keyUp events.
Something like KeymapManager is on the way from Eddy to cater for key mapping where necessary.
Updated by Matthew Iselin about 1 year ago
- Category set to Kernel
- Status changed from Assigned to Closed
- Target version set to Foster Post-Release Milestone #1
- % Done changed from 40 to 100
HID is now in a module, the HID InputManager works fine, and the generic InputManager works very well in both userspace and the kernel.
Bugs and feature requests related to InputManager need to into new tracker items, this item is now closed.