247ab65a4985470feff9cb5b5d40d2b8c64f5ada |
|
25-Apr-2014 |
Craig Mautner <cmautner@google.com> |
Throw exception from startActivity if not allowed. The ActivityView.startActivity method may defer calling ActivityContainer.startActivity if the ActivityView is not yet visible. If the activity being started doesn't have allowEmbedded attribute set to true then the SecurityException will not be thrown until the ActivityView is visible. In such a case the caller of ActivityView.startActivity cannot catch the SecurityException. This fix checks the attribute at the time ActivityView.startActivity is called. Fixes bug 14317210. Change-Id: I7fff23e39b67a9a0aa1b2e555920d02ae38906d9
/frameworks/base/core/java/android/app/IActivityContainer.aidl
|
f4c909bcb87d6f103c9f9e8255fa61bd86f4de67 |
|
18-Apr-2014 |
Craig Mautner <cmautner@google.com> |
Fix ActivityView lifecycle Major changes to maintain the VirtualDisplay across repeated attach/detach cycles of an ActivityView. This keeps the activities and VirtualDisplays in the ActivityView from getting into bad states. Fixes bug 14107002. Change-Id: Idc2aaf85ac496eab0eeb436736cb10a2020040e8
/frameworks/base/core/java/android/app/IActivityContainer.aidl
|
38f96e5020b3e82b98fe97b0be363a5ad185860f |
|
11-Feb-2014 |
Jeff Brown <jeffbrown@google.com> |
Add support for injecting events into ActivityContainers. (DO NOT MERGE) Modified ActivityView to inject touch events it receives back into its activity container. The container then injects the event into the input system along with the display id of the underlying virtual display. Enhanced the input system to support concurrent dispatch of touch events on multiple displays which is required for this to work. Change-Id: I9cf1870db3be6f99a52ed9a1e3ceafe42c940093
/frameworks/base/core/java/android/app/IActivityContainer.aidl
|
df88d73092c62a1a3cd2b2056ca63ae2e70cc238 |
|
27-Jan-2014 |
Craig Mautner <cmautner@google.com> |
Add IIntentSender to ActivityContainer.startActivity PendingIntents and IntentSenders can now be launched. Still does not work once the host activity has been paused and resumed. Window manager TaskStacks now exist independently of Displays and app windows persist after Displays are removed below them. Attaching the stack to a new Display does not yet restore the windows to it. Fixes bug 12747909. Change-Id: I509007ee23fda400b353f483cf6ecce08177763b
/frameworks/base/core/java/android/app/IActivityContainer.aidl
|
34b73dfaa3a92e5a85abf62317183fb114f2ffff |
|
13-Jan-2014 |
Craig Mautner <cmautner@google.com> |
Cleanup after ActivityView - Release Surface and VirtualDisplay when shutting down ActivityView. - Shut down child stacks when relaunching parent activity. Change-Id: I60314b2b43bd2da5406cf6ec871293b5baca157c
/frameworks/base/core/java/android/app/IActivityContainer.aidl
|
4504de5d5a8e1c7dfb306b16282f348856c24764 |
|
20-Dec-2013 |
Craig Mautner <cmautner@google.com> |
Implement ActivityView. With an existing ActivityContainer a caller can now create an ActivityView which consists of a new VirtualDisplay immediately attached to the ActivityContainer. Change-Id: Id70333dcbef55d524a87df8f8c92d72ca5579364
/frameworks/base/core/java/android/app/IActivityContainer.aidl
|
e0a3884cb627efc650e19fbe76b1b3343468cf57 |
|
17-Dec-2013 |
Craig Mautner <cmautner@google.com> |
Extend stack management to other displays. - Abandon ActivityContainer.startActivity() in favor of IActivityManager.startActivityAsUserInContainer(). - Modify Am to test starting an activity on a container. - Create a DisplayContext as the base context if the activity token is on a different display. - Test for home display in more cases when manipulating home stack. - Rename mDisplayInfos => mActivityDisplays. - Create new method for moving task to front of stack regardless of which display it is on. Change-Id: I4fcb83ae844c5839ee3e2722229623d1a80ed921
/frameworks/base/core/java/android/app/IActivityContainer.aidl
|
4a1cb22056112f7ffd5f4fad8b7a092b96e7cc7b |
|
05-Dec-2013 |
Craig Mautner <cmautner@google.com> |
Pair ActivityStacks with Displays - Introduce concept of ActivityStacks residing on Displays and able to be decoupled and moved around. - Add a new interface, IActivityContainer for clients to handle ActivityStacks. - Abandon ordering of stacks based on mStackState and instead use ActivityDisplayInfo.stacks<ActivityStack> ordering. Progress towards closing bug 12078972. Change-Id: I7785b61c26dc17f432a4803eebee07c7415fcc1f
/frameworks/base/core/java/android/app/IActivityContainer.aidl
|