From d766882c913b272cc2db478d7640a317d838ebad Mon Sep 17 00:00:00 2001 From: "jcampan@chromium.org" Date: Mon, 28 Sep 2009 21:18:58 +0000 Subject: Changing the KeyboardEvent to use a KeyboardCode instead of a w_char. Led to several places where I had to switch from VK_ to VKEY_. Also cleaned-up the table view OnKeyDown method. Since TableView is a NativeControl it can use the NativeControl::OnKeyDown directly. BUG=None TEST=Make sure short-cuts works as expected, especially in the omnibox. Review URL: http://codereview.chromium.org/248010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27412 0039d316-1c4b-4281-b951-d872f2087c98 --- views/event_win.cc | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'views/event_win.cc') diff --git a/views/event_win.cc b/views/event_win.cc index 28d1330..da6457e 100644 --- a/views/event_win.cc +++ b/views/event_win.cc @@ -37,12 +37,13 @@ int Event::ConvertWindowsFlags(UINT win_flags) { return r; } -KeyEvent::KeyEvent(EventType type, int ch, int repeat_count, int message_flags) +KeyEvent::KeyEvent(EventType type, base::KeyboardCode key_code, + int repeat_count, int message_flags) : Event(type, GetKeyStateFlags()), - character_(ch), + key_code_(key_code), repeat_count_(repeat_count), message_flags_(message_flags) { - } +} int KeyEvent::GetKeyStateFlags() const { // Windows Keyboard messages don't come with control key state as parameters -- cgit v1.1