OLD | NEW |
---|---|
1 // Copyright (c) 2012 The Chromium Authors. All rights reserved. | 1 // Copyright (c) 2012 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 // Protocol for event messages. | 5 // Protocol for event messages. |
6 | 6 |
7 syntax = "proto2"; | 7 syntax = "proto2"; |
8 | 8 |
9 option optimize_for = LITE_RUNTIME; | 9 option optimize_for = LITE_RUNTIME; |
10 | 10 |
11 package remoting.protocol; | 11 package remoting.protocol; |
(...skipping 60 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... | |
72 | 72 |
73 // Defines an event that sends clipboard data between peers. | 73 // Defines an event that sends clipboard data between peers. |
74 message ClipboardEvent { | 74 message ClipboardEvent { |
75 | 75 |
76 // The MIME type of the data being sent. | 76 // The MIME type of the data being sent. |
77 optional string mime_type = 1; | 77 optional string mime_type = 1; |
78 | 78 |
79 // The data being sent. | 79 // The data being sent. |
80 optional bytes data = 2; | 80 optional bytes data = 2; |
81 } | 81 } |
82 | |
83 message TouchEventPoint { | |
84 | |
85 // The ID for the touch point. | |
86 optional uint32 id = 1; | |
87 | |
88 // The position of the touch point. | |
89 // These values on-the-wire are host coordinates. | |
90 optional float x = 2; | |
91 optional float y = 3; | |
Wez
2015/02/05 02:09:07
nit: Do these need to be floats? Chromoting works
Rintaro Kuroiwa
2015/02/06 23:35:01
As discussed offline.
Some touch event APIs mentio
| |
92 | |
93 // The size of the touch point, used to aid hit-testing. | |
94 // Scaled to match the size on host. | |
95 optional float radius_x = 4; | |
96 optional float radius_y = 5; | |
97 | |
98 // Angle in degrees from the y-axis of the touch point. | |
99 optional float angle = 6; | |
100 | |
101 // The pressure of the touch point. | |
102 // The value should be in [0.0, 1.0]. | |
103 optional float pressure = 7; | |
104 } | |
105 | |
106 message TouchEvent { | |
107 | |
108 // A START event means that this event reports all the touch points that were | |
109 // just added, e.g. a finger started touching the display. | |
110 // A MOVE event means that the touch points that have been STARTed moved, | |
111 // e.g. multiple fingers on the screen moved. | |
112 // An END event means that the touch points that have been STARTed ended. | |
113 // e.g. a finger went off the screen. | |
114 // A CANCEL event means that the touch points that have been STARTed were | |
115 // canceled, e.g. a finger went off the screen. | |
116 // Cancel event is simlar to END but slighly different. For example, Android | |
117 // MotionEvent's ACTION_CANCEL documentation mentions that a cancel should be | |
118 // treated as an ACTION_UP (END) event but might not perform the exact same | |
119 // actions as a normal ACTION_UP event. | |
120 enum TouchEventType { | |
121 TOUCH_POINT_START = 1; | |
122 TOUCH_POINT_MOVE = 2; | |
123 TOUCH_POINT_END = 3; | |
124 TOUCH_POINT_CANCEL = 4; | |
125 }; | |
126 | |
127 optional TouchEventType event_type = 1; | |
128 | |
129 // Only the changed touch points are added to this field. | |
130 // Given the existing touch point APIs (e.g. Android and PPAPI) | |
131 // for START, END, and CANCEL events the size of this field will typically be | |
132 // 1, but for MOVE events it is likely to have multiple points. | |
133 repeated TouchEventPoint touch_points = 2; | |
134 } | |
OLD | NEW |