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 |
(...skipping 61 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; | |
92 | |
93 // The size of the touch point, used to aid hit-testing. | |
94 // Unlike x,y coordinates, these will not be scaled. | |
Sergey Ulanov
2015/01/29 18:00:46
You also need rotation angle. It's not useful to s
Rintaro Kuroiwa
2015/01/30 17:57:02
Done.
| |
95 optional float radius_x = 4; | |
Sergey Ulanov
2015/01/29 18:00:46
Do we also need a field for pressure/force?
Rintaro Kuroiwa
2015/01/30 17:57:02
wez mentioned that rotation angle and pressure are
Sergey Ulanov
2015/02/02 19:32:05
We do get pressure values on Android, Web and Pepp
Rintaro Kuroiwa
2015/02/02 22:22:56
Done.
| |
96 optional float radius_y = 5; | |
97 } | |
98 | |
99 message TouchEvent { | |
100 | |
101 enum TouchEventType { | |
102 TOUCH_POINT_START = 1; | |
Sergey Ulanov
2015/01/29 18:00:46
I'm not sure I understand what these types mean. E
Rintaro Kuroiwa
2015/01/30 17:57:02
When a user starts touching a screen with a new fi
Sergey Ulanov
2015/02/02 19:32:05
I see.
What's confusing to me is that there are mu
Rintaro Kuroiwa
2015/02/02 22:22:56
Repeating myself what we discussed offline.
Corre
| |
103 TOUCH_POINT_MOVE = 2; | |
104 TOUCH_POINT_END = 3; | |
105 // Cancel event is different from END. For example, Android MotionEvent's | |
106 // ACTION_CANCEL should be treated as UP (END) but might not perform the | |
107 // same action as UP. | |
108 TOUCH_POINT_CANCEL = 4; | |
109 }; | |
110 | |
111 optional TouchEventType event_type = 1; | |
112 repeated TouchEventPoint touch_points = 2; | |
Sergey Ulanov
2015/01/29 18:00:46
Should this include all current touches or only th
Rintaro Kuroiwa
2015/01/30 17:57:02
Only those points that changed.
This seems to be t
| |
113 } | |
OLD | NEW |