IME (input method editor) support for Aura, part 3 of 3: Use ui::InputMethod in ash.

ui/aura/event.h

Index: ui/aura/event.h
diff --git a/ui/aura/event.h b/ui/aura/event.h
index 5dcb72666b0099601416b7704426210a6a30a10c..38fb5ba0587119247157400ad7710587b0a4b5d3 100644
--- a/ui/aura/event.h
+++ b/ui/aura/event.h
@@ -171,11 +171,16 @@ class AURA_EXPORT KeyEvent : public Event {
   ui::KeyboardCode key_code() const { return key_code_; }
   bool is_char() const { return is_char_; }
 
+  void set_skip_ime(bool skip_ime) { skip_ime_ = skip_ime; }
+  bool skip_ime() const { return skip_ime_; }
+
  private:
   ui::KeyboardCode key_code_;
   // True if this is a translated character event (vs. a raw key down). Both
   // share the same type: ui::ET_KEY_PRESSED.
   bool is_char_;
+  // True if the event is generated by IME.
+  bool skip_ime_;

[Yusuke Sato, 2011/12/12 07:51:53]

This flag is for resoving the sync/async issue.

[Ben Goodger (Google), 2011/12/12 16:51:03]

It'd be good to come up with a neater way to express this. What this really
means is, "when true, the event is the result of an IME translation". Can this
occur with any type of key event (e.g. both KeyDown and KeyUp)? Seems like you
could make an argument that this is a new event type. Windows treats it as such
(WM_IME_CHAR).

[Yusuke Sato, 2011/12/14 13:42:04]

Thanks for the suggestion. I've added a new event type called
TranslatedKeyEvent.

On 2011/12/12 16:51:03, Ben Goodger (Google) wrote:

 
   uint16 character_;
   uint16 unmodified_character_;