f43a33c5ea5adb8d100ab0c3da965bac33155cb8 |
|
27-Sep-2012 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #7232641: ISE crash when rotating phone in label list mode This doesn't fix the problem; I think it is an app problem. It does improve a bunch of the debugging to help better identify what is going on, and introduces some checks when adding a fragment to fail immediately if we are getting into a state when a fragment is going to be in the added list multiple times (which is pretty much guaranteed to lead to a failure at some point in the future). Change-Id: If3a8700763facd61c4505c6ff872ae66875afc8d
/frameworks/base/core/java/android/app/BackStackRecord.java
|
ee76efb74b5886f98cdfebfbefe9b69224e016fb |
|
05-Jun-2012 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #6584942 IllegalStateException: Failure saving state... ...active SuggestFragment{419494f0} has cleared index: -1 There were issues when the same fragment was removed and then added again before completely finishing the remove (such as due to a running animation). Two fixes: - Now when you call FragmentTransaction.replace() and are replacing a fragment with the same fragment, this becomes a no-op, to avoid visual artifacts in the transition and bad states. - When we are moving the fragment state up and it is currently animating away to the INITIALIZED state, we could end up making the fragment inactive as part of the cleanup. In this case it shouldn't be made inactive; we just need to initialize it but keep it active since we are going to continue to use it. Bug: 6584942 Change-Id: I8bfd73f2d8ef8f67b541b3e2525dfa5db6c3bfa5
/frameworks/base/core/java/android/app/BackStackRecord.java
|
6c285977a0dc9605348bd9530282c7d006cbf8bd |
|
30-Aug-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issues 5158104 and 4981556 (fragment problems) 5158104: com.android.contacts: java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState at android.app.FragmentManagerImpl.checkStateLoss(FragmentManager.java:1201) The ViewPager can just commit without worrying about a state loss, since it can correctly reconstruct its state later. 4981556: Fragment.mImmediateActivity doesn't get restored on orientation change I am giving up on this thing; I just don't see how it can actually be correct. So now instead of getting an exception about a dup add/remove at point of the add/remove call, this will happen later when processing the transaction. Also add an API for controlling the visibility of menus, which ViewPager can use to have the correct menus shows. And add a method to get the name of a back stack entry. Change-Id: Idcba14cfa2a172545a7a2a2c466cb49ceb789619
/frameworks/base/core/java/android/app/BackStackRecord.java
|
d04ad541def2bca8fc2d810514ee15ab97893d35 |
|
26-Jul-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #5063010: Loaders don't seem to be properly... ...retained with compatibility library Yikes, and also in the main platform...! :( Change-Id: I76ee3a9a5ba4a220c2f54d0af9cf49e3a736e7bd
/frameworks/base/core/java/android/app/BackStackRecord.java
|
47c4156567ce5abf8a6fca7fefe6ae9a20fb5117 |
|
16-Apr-2011 |
Dianne Hackborn <hackbod@google.com> |
Back-port new fragment detach APIs from support lib. This allow a much cleaner implementation of things like the fragment pager class. Change-Id: I433be3d6c24c9a059d908d442bcfddbf1e8e57e5
/frameworks/base/core/java/android/app/BackStackRecord.java
|
bc377841db05bd5197ffadb58ba52c54b2a85f16 |
|
22-Mar-2011 |
Chet Haase <chet@google.com> |
Add custom fragment anims to be run when popping backstack The previous fragment implementation allowed for animations during fragment transitions, but did not account for the different behavior of fragments when popping the back stack. In general, you probably don't want to run the same animation for putting a fragment on the stack as for popping it off, which is what happens now. For example, you might fade a fragment out when putting it on the stack. But when popping ot off, fading it out is probably not the behavior you want. The new API (setCustomAnimations() overload with two additional parameters) allows developers to specify animations to be run in the popping operation. Otherwise, the animations are null and the operation will not be animated. Change-Id: I2e132b3890838358e496149f18a25037a59990aa
/frameworks/base/core/java/android/app/BackStackRecord.java
|
327fbd2c8fa294b919475feb4c74a74ee1981e02 |
|
17-Jan-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix a bunch of API review bugs. 3362464 API REVIEW: android.content potpourri 3362445 API REVIEW: Fragment transaction stuff 3362428 API REVIEW: Fragment stuff 3362418 API REVIEW: Loader stuff 3362414 API REVIEW: android.content.pm.ActivityInfo Change-Id: I6475421a4735759b458acb67df4380cc6234f147
/frameworks/base/core/java/android/app/BackStackRecord.java
|
d2835935d2df8be70d1b37d3ef3b2fe0155b3422 |
|
14-Dec-2010 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #3258849: Grab thumbnail when exiting an app via back Also issue #3281400: Rotating a retained instance fragment leaks the fragment manager And turn off fragment debug logging. Change-Id: Ibdd7db82bb35618021bcba421ba92ced7cd691c2
/frameworks/base/core/java/android/app/BackStackRecord.java
|
30d7189067524000c738c188c4ff91f84f474d25 |
|
11-Dec-2010 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #3274841: Orientation change problem with a paused activity Plus a bunch of debug output improvements. And some new Intent helpers for dealing with restarting an app. Change-Id: I50ec56bca6a86c562156b13fe8a6fdf68038a12e
/frameworks/base/core/java/android/app/BackStackRecord.java
|
ab36acb39941ce981dddda9f9cf4d2d23a56fd26 |
|
05-Nov-2010 |
Dianne Hackborn <hackbod@google.com> |
Fixe some stuff. Addresses these bugs: 3061847 - With no headers, PreferenceActivity crashes 2888426 - minor typo in DevicePolicyManagerService.ActiveAdmin.writeToXml() 3159155 - IllegalStateException:"Can not perform this action after onSaveInstanceState" while dismissing a DialogFragment 3155995 - PopupWindow.showAtLocation does not respect LayoutParams Also tweak the new fragment APIs to use abstract classes instead of interfaces as base classes. Change-Id: I9c0b4337fe0e304b737b5f7c2762762372bb3020
/frameworks/base/core/java/android/app/BackStackRecord.java
|
0c24a5514c1ff143a223720a090b19a86a75945f |
|
04-Nov-2010 |
Adam Powell <adamp@google.com> |
Fix bug 3156280 - Fix several issues with tab navigation in action bars. Add the ability to restrict a FragmentTransaction's ability to be added to the back stack. (It doesn't make sense for tabs or other scenarios to allow this.) Change-Id: I8fa2edb5f35c365e2483010ad13eb9993f5e6570
/frameworks/base/core/java/android/app/BackStackRecord.java
|
c6669ca63299219d815464129dac051ab2404286 |
|
16-Sep-2010 |
Dianne Hackborn <hackbod@google.com> |
Add API for showing breadcrumbs of fragment back stack. This adds a simple API to have your back stack automatically shown as bread crumbs in the action bar. Introduces some APIs to retrieve the current back stack. Also fix a little bug in the "activated" state where it was being propagated down the hierarchy as "selected". :p And from that, fix the standard colors to be reasonable when in the activated state. Finally PreferenceActivity is updated to take advantage of bread crumbs to show your place in the preferences. Change-Id: I9d633bedf8d7c6e4ed9b25cb9698faa66c7dd9a4
/frameworks/base/core/java/android/app/BackStackRecord.java
|