Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(73)

Side by Side Diff: content/common/input_messages.h

Issue 2621303004: Keep track of coalesced events in main thread event queue (Closed)
Patch Set: Improve MainThreadEventQueue unittests Created 3 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 // Copyright (c) 2013 The Chromium Authors. All rights reserved. 1 // Copyright (c) 2013 The Chromium Authors. All rights reserved.
2 // Use of this source code is governed by a BSD-style license that can be 2 // Use of this source code is governed by a BSD-style license that can be
3 // found in the LICENSE file. 3 // found in the LICENSE file.
4 4
5 // IPC messages for input events and other messages that require processing in 5 // IPC messages for input events and other messages that require processing in
6 // order relative to input events. 6 // order relative to input events.
7 // Multiply-included message file, hence no include guard. 7 // Multiply-included message file, hence no include guard.
8 8
9 #include "base/strings/string16.h" 9 #include "base/strings/string16.h"
10 #include "build/build_config.h" 10 #include "build/build_config.h"
(...skipping 114 matching lines...) Expand 10 before | Expand all | Expand 10 after
125 IPC_STRUCT_TRAITS_BEGIN(content::InputEventAck) 125 IPC_STRUCT_TRAITS_BEGIN(content::InputEventAck)
126 IPC_STRUCT_TRAITS_MEMBER(source) 126 IPC_STRUCT_TRAITS_MEMBER(source)
127 IPC_STRUCT_TRAITS_MEMBER(type) 127 IPC_STRUCT_TRAITS_MEMBER(type)
128 IPC_STRUCT_TRAITS_MEMBER(state) 128 IPC_STRUCT_TRAITS_MEMBER(state)
129 IPC_STRUCT_TRAITS_MEMBER(latency) 129 IPC_STRUCT_TRAITS_MEMBER(latency)
130 IPC_STRUCT_TRAITS_MEMBER(overscroll) 130 IPC_STRUCT_TRAITS_MEMBER(overscroll)
131 IPC_STRUCT_TRAITS_MEMBER(unique_touch_event_id) 131 IPC_STRUCT_TRAITS_MEMBER(unique_touch_event_id)
132 IPC_STRUCT_TRAITS_END() 132 IPC_STRUCT_TRAITS_END()
133 133
134 // Sends an input event to the render widget. 134 // Sends an input event to the render widget.
135 IPC_MESSAGE_ROUTED3(InputMsg_HandleInputEvent, 135 IPC_MESSAGE_ROUTED4(InputMsg_HandleInputEvent,
136 IPC::WebInputEventPointer /* event */, 136 IPC::WebInputEventPointer /* event */,
137 std::vector<IPC::WebInputEventPointer> /* coalesced ones*/,
137 ui::LatencyInfo /* latency_info */, 138 ui::LatencyInfo /* latency_info */,
138 content::InputEventDispatchType) 139 content::InputEventDispatchType)
139 140
140 // Sends the cursor visibility state to the render widget. 141 // Sends the cursor visibility state to the render widget.
141 IPC_MESSAGE_ROUTED1(InputMsg_CursorVisibilityChange, 142 IPC_MESSAGE_ROUTED1(InputMsg_CursorVisibilityChange,
142 bool /* is_visible */) 143 bool /* is_visible */)
143 144
144 // Sets the text composition to be between the given start and end offsets in 145 // Sets the text composition to be between the given start and end offsets in
145 // the currently focused editable field. 146 // the currently focused editable field.
146 IPC_MESSAGE_ROUTED3(InputMsg_SetCompositionFromExistingText, 147 IPC_MESSAGE_ROUTED3(InputMsg_SetCompositionFromExistingText,
(...skipping 169 matching lines...) Expand 10 before | Expand all | Expand 10 after
316 // This IPC message sends the character bounds after every composition change 317 // This IPC message sends the character bounds after every composition change
317 // to always have correct bound info. 318 // to always have correct bound info.
318 IPC_MESSAGE_ROUTED2(InputHostMsg_ImeCompositionRangeChanged, 319 IPC_MESSAGE_ROUTED2(InputHostMsg_ImeCompositionRangeChanged,
319 gfx::Range /* composition range */, 320 gfx::Range /* composition range */,
320 std::vector<gfx::Rect> /* character bounds */) 321 std::vector<gfx::Rect> /* character bounds */)
321 322
322 // Adding a new message? Stick to the sort order above: first platform 323 // Adding a new message? Stick to the sort order above: first platform
323 // independent InputMsg, then ifdefs for platform specific InputMsg, then 324 // independent InputMsg, then ifdefs for platform specific InputMsg, then
324 // platform independent InputHostMsg, then ifdefs for platform specific 325 // platform independent InputHostMsg, then ifdefs for platform specific
325 // InputHostMsg. 326 // InputHostMsg.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698