- Jan 23, 2014
-
-
Jean Chalard authored
Bug: 8636060 Change-Id: I624a45500603dfad355ee3b8b794b2d895219c0b
-
Jean Chalard authored
Bug: 8636060 Change-Id: I242b7c264abf380bcd6b6b3c848238921f988e54
-
Jean Chalard authored
Bug: 8636060 Change-Id: Ib13a54854e30afb79217a0a1f2aeca50a95ba155
-
Jean Chalard authored
Bug: 8636060 Change-Id: I3b144993e2bcd552f9b292b8f057c9db4216125c
-
- Jan 22, 2014
-
-
Jean Chalard authored
This works because getKey{X,Y} is a no-op on Constants.NOT_A_COORDINATE. Bug: 8636060 Change-Id: I2f7dd96b6011f094110f7978f8ff24ef2a6e2585
-
Jean Chalard authored
Bug: 8636060 Change-Id: Ic051e5d5514d270101b0571a2d30e2caa8f85bc1
-
Jean Chalard authored
This also fixes the coordinates passed to logOnDelete and log onSeparator. Bug: 8636060 Change-Id: I4703d61ad7de76b501adca18df3a69e06450c9a1
-
Jean Chalard authored
This is fine because getKey{X,Y} is idempotent for any non-keyboard coordinate value. However this makes a net change : the x,y values passed to LatinImeLoggerUtils.onNonSeparator are now different. The point is however that they used to be wrong. The logged values used not to account for the keyboard padding that is present on tablets, and in the simulating tools we don't know about that padding so we couldn't use the coordinates. The catch here is that other calls like LoggerUtils.onSeparator should follow suit, but this is too big a change to do it at once. Follow-up changes will fix them too. Bug: 8636060 Change-Id: If4b3d3cb1ed4b44c35f23e66aba3b5797236bba7
-
Jean Chalard authored
-
- Jan 20, 2014
-
-
Keisuke Kuroyanagi authored
-
Keisuke Kuroyanagi authored
Change-Id: I03e5c8f95cb22c7096ff545f1181f914b80a6c58
-
Tadashi G. Takaoka authored
-
Tadashi G. Takaoka authored
Change-Id: I4103541d99fe59bfcf12379a1298a0a690497846
-
Tadashi G. Takaoka authored
The newline string resource "\n" doesn't work off-device simulation. Bug: 12623502 Change-Id: I3ad63d8afe50be174493d43f00f7191062c87cb7
-
Tadashi G. Takaoka authored
-
Tadashi G. Takaoka authored
Change-Id: I78d488ad84a11af809ee1f8d3d2fa01a89fbfa28
-
Tadashi G. Takaoka authored
Change-Id: Ic7d2cbb2c1b2deaa4e735484bdc7413c0b3b1939
-
- Jan 19, 2014
-
-
Keisuke Kuroyanagi authored
-
Keisuke Kuroyanagi authored
Change-Id: I2d2d226e21a46239077394ab09db88a4bd563460
-
- Jan 17, 2014
-
-
Keisuke Kuroyanagi authored
-
Keisuke Kuroyanagi authored
Bug: 12515251 Change-Id: I0b332e03b9102957bffaea56d4de17b9ee3cef23
-
Tadashi G. Takaoka authored
Change-Id: I866488a47ca04ca587e805663dfd597bb7b1ebce
-
Jean Chalard authored
-
- Jan 16, 2014
-
-
Jean Chalard authored
-
Jean Chalard authored
-
Jean Chalard authored
-
Keisuke Kuroyanagi authored
-
Jean Chalard authored
Bug: 8636060 Change-Id: Id87b0ac4a99ec6a26db6e250d6cd22defc02a23d
-
Jean Chalard authored
Yay Bug: 8636060 Change-Id: Iad9c3804504635094e861999198f4baf70e61955
-
Jean Chalard authored
Um... this is not async ? Remove that from the name Bug: 8636060 Change-Id: Ida5f9bd6929eae75103eb2e3fb866ed7468af806
-
Jean Chalard authored
No need to test multiple times for this. Let's just never do useless stuff, and only test for that once. Bug: 8636060 Change-Id: I50a9e4da769fbec44fbb12eedfed03aad924cc2c
-
Jean Chalard authored
Bug: 9663105 Change-Id: Ib68ee4edb135e96dfca229c1ccce308e7e638bdd
-
Tadashi G. Takaoka authored
This CL fix the checkbuild build, though I'm not sure it can create working dicttool or not. Change-Id: I5aec34a0f72441c75ac48184c0550b8e0fc40634
-
Keisuke Kuroyanagi authored
-
Keisuke Kuroyanagi authored
Change-Id: I512c41e12d8d31f03b5df6ad03bf7711611c80f5
-
Geoff Mendal authored
-
Geoff Mendal authored
Change-Id: I9d276ae4391f209e2db3a080b3221e5a8aa59938 Auto-generated-cl: translation import
-
- Jan 15, 2014
-
-
Keisuke Kuroyanagi authored
Bug: 12443085 Change-Id: I41a5cf6c895cb59e54af98b40efded36afcd3247
-
Jean Chalard authored
-
Jean Chalard authored
-