Consolidate OnKeyEvent and InputMethod code.

views/ime/input_method_delegate.h

Index: views/ime/input_method_delegate.h
diff --git a/views/ime/input_method_delegate.h b/views/ime/input_method_delegate.h
index 70d2ac36cefb78fede072e298f09db23a263b679..781db5284ef457568acc21387812968ad01d8ecc 100644
--- a/views/ime/input_method_delegate.h
+++ b/views/ime/input_method_delegate.h
@@ -19,7 +19,7 @@ class InputMethodDelegate {
   virtual ~InputMethodDelegate() {}
 
   // Dispatch a key event already processed by the input method.
-  virtual void DispatchKeyEventPostIME(const KeyEvent& key) = 0;
+  virtual bool DispatchKeyEventPostIME(const KeyEvent& key) = 0;

[Ben Goodger (Google), 2011/04/15 18:23:19]

Do you even still need this function?

I was thinking InputMethod::OnKeyEvent would return a bool indicating whether or
not the calling Widget should process further... which is effectively what this
function is doing. If you remove this then you can delete the whole delegate
interface.

[msw, 2011/04/15 19:19:57]

According to James, it's necessary, although I'm still unclear about exactly
why, see the included e-mail exchange.

Shall I invert the return value? Returning 'handled' (or 'no further handling
required') is a more common practice and semantically assumes less about the
caller's behavior.

 
 };