Index: remoting/proto/control.proto |
diff --git a/remoting/proto/control.proto b/remoting/proto/control.proto |
index 20f0b9d4b9b24a37fa09fbd33cf2d1dc17b9bd9c..e1c29ce3a01d7bf6c5c785e5e88840c106c81c72 100644 |
--- a/remoting/proto/control.proto |
+++ b/remoting/proto/control.proto |
@@ -10,10 +10,19 @@ option optimize_for = LITE_RUNTIME; |
package remoting.protocol; |
-message ClientDimensions { |
- // Width and height of the client. |
- optional int32 width = 1; |
- optional int32 height = 2; |
+message ClientResolution { |
+ // Legacy width and height of the client in Density-Independent Pixels |
+ optional int32 dips_width = 1; |
+ optional int32 dips_height = 2; |
Jamie
2013/02/11 23:25:58
I assume the names are only important for the acce
Wez
2013/02/12 01:55:28
The numbers identify the fields at the protocol le
|
+ |
+ // Width and height of the client in device pixels. |
+ optional int32 width = 3; |
+ optional int32 height = 4; |
+ |
+ // Horizontal and vertical DPI of the screen. If either of these is zero or |
+ // unset, the corresponding DPI should be assumed to be 96 (Windows' default) |
+ optional int32 x_dpi = 5; |
+ optional int32 y_dpi = 6; |
} |
message VideoControl { |