package proto.input

Get desktop application:
View/edit binary Protocol Buffers messages

Client -> Host (channel 5).

• optional MouseEvent mouse = 1

• optional KeyEvent key = 2

• optional TouchEvent touch = 3

• optional TextEvent text = 4

Used in: ClientToHost, legacy.ClientToSession

• uint32 usb_keycode = 1

• uint32 flags = 2

The keyboard (Caps/Num) lock states.

• UNKNOWN = 0

• CAPSLOCK = 1

• NUMLOCK = 2

• PRESSED = 4

Used in: ClientToHost, legacy.ClientToSession

• uint32 mask = 1

  Button mask.

• int32 x = 2

  x position.

• int32 y = 3

  y position.

• EMPTY = 0

• LEFT_BUTTON = 1

• MIDDLE_BUTTON = 2

• RIGHT_BUTTON = 4

• WHEEL_UP = 8

• WHEEL_DOWN = 16

• BACK_BUTTON = 32

• FORWARD_BUTTON = 64

Used in: ClientToHost, legacy.ClientToSession

• string text = 1

Used in: ClientToHost, legacy.ClientToSession

• TouchEvent.TouchEventType event_type = 1

• repeated TouchEventPoint touch_points = 2

  Only the changed touch points are added to this field. Given the existing touch point APIs (e.g. Android and PPAPI) for START, END, and CANCEL events the size of this field will typically be 1, but for MOVE events it is likely to have multiple points.

A START event means that this event reports all the touch points that were just added, e.g. a finger started touching the display. A MOVE event means that the touch points that have been STARTed moved, e.g. multiple fingers on the screen moved. An END event means that the touch points that have been STARTed ended. e.g. a finger went off the screen. A CANCEL event means that the touch points that have been STARTed were canceled, e.g. a finger went off the screen. Cancel event is simlar to END but slighly different. For example, Android MotionEvent's ACTION_CANCEL documentation mentions that a cancel should be treated as an ACTION_UP (END) event but might not perform the exact same actions as a normal ACTION_UP event.

Used in: TouchEvent

• TOUCH_POINT_UNKNOWN = 0

• TOUCH_POINT_START = 1

• TOUCH_POINT_MOVE = 2

• TOUCH_POINT_END = 3

• TOUCH_POINT_CANCEL = 4

Used in: TouchEvent

• uint32 id = 1

  The ID for the touch point.

• float x = 2

  The absolute position of the touch point. These values on-the-wire are host physical pixel coordinates: the top-left monitor on the system always starts from (0, 0).

• float y = 3

• float radius_x = 4

  The size of the touch point, used to aid hit-testing. Scaled to match the size on host.

• float radius_y = 5

• float angle = 6

  Angle in degrees from the y-axis of the touch point.

• float pressure = 7

  The pressure of the touch point. The value should be in [0.0, 1.0].