a8bfeaf4f49fa33e96f37302f9c9b99c94aa1581 |
|
15-Mar-2012 |
Romain Guy <romainguy@google.com> |
Cleanup ListView glow's optimized invalidates Change-Id: Ie9759fd95366866512ec55072aa482f972650d15
/frameworks/base/core/java/android/widget/EdgeEffect.java
|
9d849a2f6351caed83105b90cab79223ec2bfbd3 |
|
15-Mar-2012 |
Romain Guy <romainguy@google.com> |
Optimize invalidate calls in lists. AbsListView was doing too many invalidates during scrolls/flings. Some of them were also covering too large an area of the screen. Change-Id: I68fe5dda3657bddd673996e7cf4f3c3672c66cfc
/frameworks/base/core/java/android/widget/EdgeEffect.java
|
539ee8716b4f81260bab2e9f3dc5d88d81c99985 |
|
04-Feb-2012 |
Adam Powell <adamp@google.com> |
Add transient state tracking to Views Transient state is temporary bookkeeping that Views need to perform that the app should not need to be aware of. Examples include text selection regions and animation state. Transient state is a problem for AdapterViews like ListView that do view recycling. Unless the app takes responsibility for tracking and restoring transient state as if it were a part of the adapter's data set, it cannot correctly recycle views. Selections disappear when an EditText is scrolled out of sight and animations seem to play on the wrong views. Views can now flag themselves as having transient state. (As the name implies, this should be a temporary condition.) If a ViewGroup contains a child with transient state, that ViewGroup also has transient state. AbsListView's recycler now tracks views with transient state separately. Views with transient state will be retained, and until a data set change occurs the same view will be reused for that position instead of calling the adapter's getView() method. The API to set and check transient state is currently hidden. Change-Id: Idfd8eaac2c548337686d8d9f98fda4c64be5b8a0
/frameworks/base/core/java/android/widget/EdgeEffect.java
|
1373a8eb581fe3c8e9a036e69042015f98a7e346 |
|
11-Nov-2011 |
Christopher Tate <ctate@google.com> |
Localized optimizations in views and bitmaps * Don't call context.getResources() redundantly when unnecessary; similarly for Resources.getCompatibilityInfo() * During bitmap creation, don't bother clearing to 0: it's unnecessary because now that the raw bits are stored in a VM-side byte array, it was cleared at initialization time. Also, don't use the sanity- checking public entry point to erase to a color, because we know that we're by definition in a "legal" path to erase to the initial contents and don't need to incur the overhead of the (inappropriate) sanity checking. Change-Id: Idaca4d64fdecefd5d51337646ead32e1db510e02
/frameworks/base/core/java/android/widget/EdgeEffect.java
|
89935e41c593a599e8955388b27fb926e60e5e94 |
|
31-Aug-2011 |
Adam Powell <adamp@google.com> |
Make EdgeEffect public API. This enables apps to make use of the system's visual edge effect used during overscroll in 2D content. Also un-@hide the getCurrVelocity methods from Scroller/OverScroller, without which it becomes cumbersome to obtain values to pass to the EdgeEffect#onAbsorb method. Change-Id: I40e452455f5cb5d45d1fb3687f739fc8eae65560
/frameworks/base/core/java/android/widget/EdgeEffect.java
|