Comment 60 for bug 201887
Revision history for this message
| Edwin Erdmanis (edwin-erdmanis) wrote | #60 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
@Frédéric Grosshans:
Thank you for taking care of the housekeeping :) Will make an effort to stay on topic:
I believe that any work/patches that were done for MacBooks are actually working fine: Macbook users seem to be happy with the state of the current kernel as above. The problem seems to only effect users of the slim USB keyboards(such as myself).
It has been mentioned that the driver(not sure?) should detect whether the Apple Inc. keyboard is either the Macbook, or USB/External type and adapt it's behavior accordingly.
For the USB slim keyboard, IMHO, num-lock is not needed at all. There are no arrows marked on the num-pad and therefore arrow function on the num-pad is of no use. The num-lock/clear key should definitely *NOT* change the behavior of the alpha-num keys, as it unfortunately does currently - this is the specific problem I believe.