Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(360)

Side by Side Diff: ui/events/keycodes/keyboard_code_conversion.h

Issue 24257011: Revert "Revert 224496 "Move ui/base/latency_info* to ui/events"" (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Fix gyp bustage Created 7 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « ui/events/events_export.h ('k') | ui/events/keycodes/keyboard_code_conversion_android.h » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 // Copyright (c) 2011 The Chromium Authors. All rights reserved. 1 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 #ifndef UI_EVENTS_KEYCODES_KEYBOARD_CODE_CONVERSION_H_ 5 #ifndef UI_EVENTS_KEYCODES_KEYBOARD_CODE_CONVERSION_H_
6 #define UI_EVENTS_KEYCODES_KEYBOARD_CODE_CONVERSION_H_ 6 #define UI_EVENTS_KEYCODES_KEYBOARD_CODE_CONVERSION_H_
7 7
8 #include "base/basictypes.h" 8 #include "base/basictypes.h"
9 #include "ui/base/ui_export.h" 9 #include "ui/events/events_export.h"
10 #include "ui/events/keycodes/keyboard_codes.h" 10 #include "ui/events/keycodes/keyboard_codes.h"
11 11
12 namespace ui { 12 namespace ui {
13 13
14 // A helper function to get the character generated by a key event in a 14 // A helper function to get the character generated by a key event in a
15 // platform independent way. It supports control characters as well. 15 // platform independent way. It supports control characters as well.
16 // It assumes a US keyboard layout is used, so it may only be used when there 16 // It assumes a US keyboard layout is used, so it may only be used when there
17 // is no native event or no better way to get the character. 17 // is no native event or no better way to get the character.
18 // For example, if a virtual keyboard implementation can only generate key 18 // For example, if a virtual keyboard implementation can only generate key
19 // events with key_code and flags information, then there is no way for us to 19 // events with key_code and flags information, then there is no way for us to
20 // determine the actual character that should be generate by the key. Because 20 // determine the actual character that should be generate by the key. Because
21 // a key_code only represents a physical key on the keyboard, it has nothing 21 // a key_code only represents a physical key on the keyboard, it has nothing
22 // to do with the actual character printed on that key. In such case, the only 22 // to do with the actual character printed on that key. In such case, the only
23 // thing we can do is to assume that we are using a US keyboard and get the 23 // thing we can do is to assume that we are using a US keyboard and get the
24 // character according to US keyboard layout definition. 24 // character according to US keyboard layout definition.
25 // If a virtual keyboard implementation wants to support other keyboard 25 // If a virtual keyboard implementation wants to support other keyboard
26 // layouts, that may generate different text for a certain key than on a US 26 // layouts, that may generate different text for a certain key than on a US
27 // keyboard, a special native event object should be introduced to carry extra 27 // keyboard, a special native event object should be introduced to carry extra
28 // information to help determine the correct character. 28 // information to help determine the correct character.
29 // Take XKeyEvent as an example, it contains not only keycode and modifier 29 // Take XKeyEvent as an example, it contains not only keycode and modifier
30 // flags but also group and other extra XKB information to help determine the 30 // flags but also group and other extra XKB information to help determine the
31 // correct character. That's why we can use XLookupString() function to get 31 // correct character. That's why we can use XLookupString() function to get
32 // the correct text generated by a X key event (See how is GetCharacter() 32 // the correct text generated by a X key event (See how is GetCharacter()
33 // implemented in event_x.cc). 33 // implemented in event_x.cc).
34 UI_EXPORT uint16 GetCharacterFromKeyCode(KeyboardCode key_code, int flags); 34 EVENTS_EXPORT uint16 GetCharacterFromKeyCode(KeyboardCode key_code, int flags);
35 35
36 } // namespace ui 36 } // namespace ui
37 37
38 #endif // UI_EVENTS_KEYCODES_KEYBOARD_CODE_CONVERSION_H_ 38 #endif // UI_EVENTS_KEYCODES_KEYBOARD_CODE_CONVERSION_H_
OLDNEW
« no previous file with comments | « ui/events/events_export.h ('k') | ui/events/keycodes/keyboard_code_conversion_android.h » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698