Clicking on the control area of a window should bring it to
the top and set the focus since it might be used as a drag
operation which would move / resize it.
Bug: 23179116
Change-Id: I672bfefa42dd85e962fe343aeb89167ce125f168
If an event makes it into the NonClientDecor and the
application is maximized, it should not process it.
Bug: 23489031
Change-Id: I661ea207522bbea64f297cd63cc2b5da192d47ae
The GestureLaunchService now informs systemUI that a launch
has been requested and the systemUI, depending on its state
will launch the Camera in the correct mode, including
animations.
Bug: 22957192
Bug: 22958025
Change-Id: I815437c8bd33638245ac61a750f64af74fe3e1e3
INVALID_STACK_ID from getWorkspaceId when there is no associated
workspace. This leaves the caller free to default.
PhoneWindow: Default to FULLSCREEN_WORKSPACE_STACK_ID in the case
of INVALID_STACK_ID returned from the ActivityManagerService.
Bug: #23171731
Change-Id: Id5132337459bd2ef81b2416434d7657b6f3d1855
This CL adds the necessary hooks between PhoneWindowManager
and SysUI to show a keyboard shortcuts screen given a specific
shortcut combination. SysUI for now just shows a Toast.
Change-Id: Icf43a81776b04a2e96a540f45b7cd3464342d679
This patch adds the capability to move / drag a floating window on
the desktop when it has a non client decor capition.
It also adds the framework necessary adjustments to keep the window
in a visible area without relayout'ing the window upon move.
Bug: 21738328
Bug: 23176762
Change-Id: I0927e98902d8172f58d21c19c249936a81181678
INPUT_METHOD_SEPARATOR and INPUT_METHOD_SUBTYPE_SEPARATOR are defined in
both InputMethodUtils and InputMethodSettings with same value.
This CL removes definitions in InputMethodSettings and use SEPARATOR
instead of SEPARATER.
INPUT_METHOD_SEPARATOR and INPUT_METHOD_SUBTYPE_SEPARATOR in
InputMethodUtils are originally introduced to IMMS by
If0104151b3526da6ecc669adde3119a239ecafeb and they are moved to
InputMethodUtils by I01f5fafbbcfe3e3f5313829162ec011eaf2ad991.
INPUT_METHOD_SEPARATER and INPUT_METHOD_SUBTYPE_SEPARATER in
InputMethodSettings are originally introducced to IMMS as a part of
IMMS.InputMethodSettings by Icd0f13de396ce286ff6563e8c2775d53bcdacbf3
and InputMethodSettings is moved to InputMethodSettings by
I0bc9954f163a3ec38d08b9ba842a8a31176eb6a6
Bug: 22285167
Change-Id: I3601c10902b44bb639581e3b816a3fc0a4851957
Removed in change Ic4cb43e7. I could switch back to the HSV
methods or just do the lazy thing and copy the code in like
in change Iae3d85c0. (Obviously I chose the latter.)
Change-Id: I154626c326ee0bbf389df75f4a8050136b56c2d5
This changes debug message format but does not change any other behavior.
Maintaining InputMethodUtils.getStackTrace() doesn't make much sense
because we already have a similar method in android.os.Debug.
since there is already utility function in Android. The length 10 is
sufficient for identifying caller modules.
getStackTrace() is introduced by
Ib23849d352db33f0747aa9d5a178f00ac726c13b just for debugging purpose as a
part of Bug 6931482.
Bug: 22285167
Change-Id: If3a6c0d2f51dc3774eef14b4f496b5b59ddcf5a6
This CL is mechanical code moving and does not change any existing
semantics.
parseInputMethodsAndSubtypesString is introduced by
If0104151b3526da6ecc669adde3119a239ecafeb for addressing Bug 19822542.
This code moving is one of the TODOs in above change.
Bug: 22285167
Change-Id: I01f5fafbbcfe3e3f5313829162ec011eaf2ad991
