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

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

Issue 2479123003: WIP Add getCoalescedEvents API using vector of WebInputEvents (Closed)
Patch Set: Creating CoalescedWebInputEvent Created 4 years, 1 month 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 109 matching lines...) Expand 10 before | Expand all | Expand 10 after
120 IPC_STRUCT_TRAITS_BEGIN(content::InputEventAck) 120 IPC_STRUCT_TRAITS_BEGIN(content::InputEventAck)
121 IPC_STRUCT_TRAITS_MEMBER(source) 121 IPC_STRUCT_TRAITS_MEMBER(source)
122 IPC_STRUCT_TRAITS_MEMBER(type) 122 IPC_STRUCT_TRAITS_MEMBER(type)
123 IPC_STRUCT_TRAITS_MEMBER(state) 123 IPC_STRUCT_TRAITS_MEMBER(state)
124 IPC_STRUCT_TRAITS_MEMBER(latency) 124 IPC_STRUCT_TRAITS_MEMBER(latency)
125 IPC_STRUCT_TRAITS_MEMBER(overscroll) 125 IPC_STRUCT_TRAITS_MEMBER(overscroll)
126 IPC_STRUCT_TRAITS_MEMBER(unique_touch_event_id) 126 IPC_STRUCT_TRAITS_MEMBER(unique_touch_event_id)
127 IPC_STRUCT_TRAITS_END() 127 IPC_STRUCT_TRAITS_END()
128 128
129 // Sends an input event to the render widget. 129 // Sends an input event to the render widget.
130 IPC_MESSAGE_ROUTED3(InputMsg_HandleInputEvent, 130 IPC_MESSAGE_ROUTED4(InputMsg_HandleInputEvent,
131 IPC::WebInputEventPointer /* event */, 131 IPC::WebInputEventPointer /* event */,
132 std::vector<IPC::WebInputEventPointer> /* coalesced evts */,
132 ui::LatencyInfo /* latency_info */, 133 ui::LatencyInfo /* latency_info */,
133 content::InputEventDispatchType) 134 content::InputEventDispatchType)
134 135
135 // Sends the cursor visibility state to the render widget. 136 // Sends the cursor visibility state to the render widget.
136 IPC_MESSAGE_ROUTED1(InputMsg_CursorVisibilityChange, 137 IPC_MESSAGE_ROUTED1(InputMsg_CursorVisibilityChange,
137 bool /* is_visible */) 138 bool /* is_visible */)
138 139
139 // Sets the text composition to be between the given start and end offsets in 140 // Sets the text composition to be between the given start and end offsets in
140 // the currently focused editable field. 141 // the currently focused editable field.
141 IPC_MESSAGE_ROUTED3(InputMsg_SetCompositionFromExistingText, 142 IPC_MESSAGE_ROUTED3(InputMsg_SetCompositionFromExistingText,
(...skipping 172 matching lines...) Expand 10 before | Expand all | Expand 10 after
314 // This IPC message sends the character bounds after every composition change 315 // This IPC message sends the character bounds after every composition change
315 // to always have correct bound info. 316 // to always have correct bound info.
316 IPC_MESSAGE_ROUTED2(InputHostMsg_ImeCompositionRangeChanged, 317 IPC_MESSAGE_ROUTED2(InputHostMsg_ImeCompositionRangeChanged,
317 gfx::Range /* composition range */, 318 gfx::Range /* composition range */,
318 std::vector<gfx::Rect> /* character bounds */) 319 std::vector<gfx::Rect> /* character bounds */)
319 320
320 // Adding a new message? Stick to the sort order above: first platform 321 // Adding a new message? Stick to the sort order above: first platform
321 // independent InputMsg, then ifdefs for platform specific InputMsg, then 322 // independent InputMsg, then ifdefs for platform specific InputMsg, then
322 // platform independent InputHostMsg, then ifdefs for platform specific 323 // platform independent InputHostMsg, then ifdefs for platform specific
323 // InputHostMsg. 324 // InputHostMsg.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698