Add initial support for handling touch events in desktop chrome AURA.

ui/views/widget/native_widget_win.cc

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "ui/views/widget/native_widget_win.h"
 
 #include <dwmapi.h>
 #include <shellapi.h>
 
 #include <algorithm>
@@ skipping 763 matching lines @@
   return event.handled();
 }
 
 bool NativeWidgetWin::HandleUntranslatedKeyEvent(const ui::KeyEvent& event) {
   InputMethod* input_method = GetInputMethod();
   if (input_method)
     input_method->DispatchKeyEvent(event);
   return !!input_method;
 }
 
+bool NativeWidgetWin::HandleTouchEvent(const ui::TouchEvent& event) {
+  delegate_->OnTouchEvent(const_cast<ui::TouchEvent*>(&event));

[sky, 2013/01/07 15:53:45]

Does this mean windows is now going to start generating touch events? And won't
views get both a touch and mouse event?

[ananta, 2013/01/08 00:50:22]

As per our discussion, added checks in hwnd_message_handler to send touch events
only for AURA and to ignore Windows synthesized mouse messages.

+  return event.handled();
+}
+
 bool NativeWidgetWin::HandleIMEMessage(UINT message,
                                        WPARAM w_param,
                                        LPARAM l_param,
                                        LRESULT* result) {
   InputMethod* input_method = GetInputMethod();
   if (!input_method || input_method->IsMock()) {
     *result = 0;
     return false;
   }
 
@@ skipping 236 matching lines @@
 // static
 bool NativeWidgetPrivate::IsTouchDown() {
   // This currently isn't necessary because we're not generating touch events on
   // windows.  When we do, this will need to be updated.
   return false;
 }
 
 }  // namespace internal
 
 }  // namespace views