Ozone X11 platform

ui/events/event.cc

Index: ui/events/event.cc
diff --git a/ui/events/event.cc b/ui/events/event.cc
index 894d5b0f2aded44d4880e4ce2d25b043c4d4477e..6ab9a85f75edb7496bdc2e17d59fddeb2f23fb2f 100644
--- a/ui/events/event.cc
+++ b/ui/events/event.cc
@@ -77,6 +77,7 @@ std::string EventTypeName(ui::EventType type) {
     CASE_TYPE(ET_SCROLL_FLING_CANCEL);
     CASE_TYPE(ET_CANCEL_MODE);
     CASE_TYPE(ET_UMA_DATA);
+    CASE_TYPE(ET_X_RAW_EVENT);

[spang, 2014/11/24 18:56:54]

This is essentially just native_event() spelled differently. We've been trying
to take a principled stance on removing that.

If did want to break that principle, the right thing to do would be to allow
NativeEvent to be an opaque pointer in ozone builds and add a generic way to
build a ui::Event out of it.

However my sense is still that we should concentrate on removing it.

[achaulk, 2014/11/24 19:28:39]

Yes, but there are some messages that need to be passed up to the window
implementation as-is. I could add ET_FOCUS_OUT, ET_EXPOSE, ET_CONFIGURE,
ET_CLIENT_MESSAGE and appropriate structs... but those are still X specific
abstractions anyway, and CLIENT_MESSAGE is just another name for NativeEvent too

     case ui::ET_LAST: NOTREACHED(); return std::string();
     // Don't include default, so that we get an error when new type is added.
   }
@@ -976,4 +977,12 @@ GestureEvent::GestureEvent(float x,
 GestureEvent::~GestureEvent() {
 }
 
+CustomEvent::CustomEvent(EventType type,
+                         base::TimeDelta time_stamp,
+                         void* generic_event_data)
+    : Event(type, time_stamp, 0), generic_event_data_(generic_event_data) {
+}
+CustomEvent::~CustomEvent() {
+}
+
 }  // namespace ui