| 2e751b8c778fd991fcdcec3bc2d1f32a722f436b |
|
17-Mar-2016 |
Andrii Kulian <akulian@google.com> |
Update ActivityInfo#WindowLayout apis (1/3)
Adds documentation, renames Layout to WindowLayout and
splits #minimalSize to #minimalWidth and #minimalHeight.
Bug: 27528326
Change-Id: Idb440cb081a14ccdc83309284e906454633c4504
/frameworks/base/services/core/java/com/android/server/am/LaunchingTaskPositioner.java
|
| d2f1d94fe5acc5d23f03bb3b653061184fd67eb5 |
|
15-Oct-2015 |
Filip Gruszczynski <gruszczy@google.com> |
API for minimal width/height of an activity.
Bug: 21409825
Change-Id: Id6286064713672366dd4dc1f80258450a8039c36
/frameworks/base/services/core/java/com/android/server/am/LaunchingTaskPositioner.java
|
| aff7f134a29d0eeac9ec07db4b97c36ecb202ea5 |
|
03-Sep-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Fix fitWithinBounds to actually apply stack bounds.
Bug: 23749629
Change-Id: Idfca4a83647c3a70c954caeca70d73aa9deee38b
/frameworks/base/services/core/java/com/android/server/am/LaunchingTaskPositioner.java
|
| ebcc875f10f05db7365cd8afbf4e9425221ab14d |
|
26-Aug-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Move Configuration creation from Window Manager to Activity Manager.
Currently the construction of configuration is split between thease
two entities. This poses two problems: it's harder to follow the
construction logic and more importantly we can't determine if
configuration changes significantly before delegating work to the
Window Manager. This CL moves the configuration override logic to
the Activity Manager, since it both detects configuration changes and
informs clients about them. Window Manager becomes purely a recipient
of the information.
Change-Id: I075570ee055cce9c5665772fa8d4fe8ccb5c6313
/frameworks/base/services/core/java/com/android/server/am/LaunchingTaskPositioner.java
|
| 9b1ce52f254b4d9c17ebf437f19f45603d3ad5b2 |
|
21-Aug-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Using initial activity layout to position the launching activity.
The activity can be positioned in the center or in one of the corners.
From there it shifts its position and tries to find a spot where it
doesn't collide with other activities.
The CL also includes a few fixes necessary to pipe the information about
the initial layout through the system.
Change-Id: I2aaf5b6d20044aafec713b7bd4193b05cfbd16f3
/frameworks/base/services/core/java/com/android/server/am/LaunchingTaskPositioner.java
|
| e5390e7379303cfef6160f4679bd7b288b57a9f8 |
|
19-Aug-2015 |
Filip Gruszczynski <gruszczy@google.com> |
Non colliding positioning of entering resizeable tasks.
When a new task enters freeform work space, it becomes full screen. This
CL makes it non fullscreen upon entry and also tries to position the
task in a way, that won't collide with existing tasks (so it's clear to
the user, that they are still there).
Change-Id: Ia04fdcadd0e85b268c323358cd4b3e04affa7939
/frameworks/base/services/core/java/com/android/server/am/LaunchingTaskPositioner.java
|