| 617feb99a06e7ffb3894e86a286bf30e085f321a |
|
10-Sep-2013 |
Alan Viverette <alanv@google.com> |
Add View constructor that supplies a default style resource
Also updates the constructor of every class that extends View.
BUG: 10676369
Change-Id: Ifaf27bf82028d180afa4931c0e906df88d858ac3
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| a6a4cbc18f7e5a3831d787d3f398e02c5eae6512 |
|
27-Sep-2012 |
Adam Cohen <adamcohen@google.com> |
Fixing Keyguard widget click handling (issue 7179972)
Change-Id: I2b268d08f5aff403a04db53c357fa45a6cb8d490
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 335c3b681bf1c118d9bf22d1a508c87173632ec6 |
|
25-Jul-2012 |
Adam Cohen <adamcohen@google.com> |
Caching the FixedSizeRemoteViewsCaches across rotation
-> This prevents unnecessary flashing of collection widgets on rotation
Change-Id: Id29d4952aa640ca90b31dc3e02e2402cc0fb84d3
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 4213804541a8b05cd0587b138a2fd9a3b7fd9350 |
|
20-Mar-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Accessibility focus - framework
Usefulness: Keep track of the current user location in the screen when
traversing the it. Enabling structural and directional
navigation over all elements on the screen. This enables
blind users that know the application layout to efficiently
locate desired elements as opposed to try touch exploring the
region where the the element should be - very tedious.
Rationale: There are two ways to implement accessibility focus One is
to let accessibility services keep track of it since they
have access to the screen content, and another to let the view
hierarchy keep track of it. While the first approach would
require almost no work on our part it poses several challenges
which make it a sub-optimal choice. Having the accessibility focus
in the accessibility service would require that service to scrape
the window content every time it changes to sync the view tree
state and the accessibility focus location. Pretty much the service
will have to keep an off screen model of the screen content. This
could be quite challenging to get right and would incur performance
cost for the multiple IPCs to repeatedly fetch the screen content.
Further, keeping virtual accessibility focus (i.e. in the service)
would require sync of the input and accessibility focus. This could
be challenging to implement right as well. Also, having an unlimited
number of accessibility services we cannot guarantee that they will
have a proper implementation, if any, to allow users to perform structural
navigation of the screen content. Assuming two accessibility
services implement structural navigation via accessibility focus,
there is not guarantee that they will behave similarly by default,
i.e. provide some standard way to navigate the screen content.
Also feedback from experienced accessibility researchers, specifically
T.V Raman, provides evidence that having virtual accessibility focus
creates many issues and it is very hard to get right.
Therefore, keeping accessibility focus in the system will avoid
keeping an off-screen model in accessibility services, it will always
be in sync with the state of the view hierarchy and the input focus.
Also this will allow having a default behavior for traversing the
screen via this accessibility focus that is consistent in all
accessibility services. We provide accessibility services with APIs to
override this behavior but all of them will perform screen traversal
in a consistent way by default.
Behavior: If accessibility is enabled the accessibility focus is the leading one
and the input follows it. Putting accessibility focus on a view moves
the input focus there. Clearing the accessibility focus of a view, clears
the input focus of this view. If accessibility focus is on a view that
cannot take input focus, then no other view should have input focus.
In accessibility mode we initially give accessibility focus to the topmost
view and no view has input focus. This ensures consistent behavior accross
all apps. Note that accessibility focus can move hierarchically in the
view tree and having it at the root is better than putting it where the
input focus would be - at the first input focusable which could be at
an arbitrary depth in the view tree. By default not all views are reported
for accessibility, only the important ones. A view may be explicitly labeled
as important or not for accessibility, or the system determines which one
is such - default. Important views for accessibility are all views that are
not dumb layout managers used only to arrange their chidren. Since the same
content arrangement can be obtained via different combintation of layout
managers, such managers cannot be used to reliably determine the application
structure. For example, a user should see a list as a list view with several
list items and each list item as a text view and a button as opposed to seeing
all the layout managers used to arrange the list item's content.
By default only important for accessibility views are regared for accessibility
purposes. View not regarded for accessibility neither fire accessibility events,
nor are reported being on the screen. An accessibility service may request the
system to regard all views. If the target SDK of an accessibility services is
less than JellyBean, then all views are regarded for accessibility.
Note that an accessibility service that requires all view to be ragarded for
accessibility may put accessibility focus on any view. Hence, it may implement
any navigational paradigm if desired. Especially considering the fact that
the system is detecting some standard gestures and delegates their processing
to an accessibility service. The default implementation of an accessibility
services performs the defualt navigation.
bug:5932640
bug:5605641
Change-Id: Ieac461d480579d706a847b9325720cb254736ebe
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| d0c735fccc904366ded657263c33bb15475a1123 |
|
24-Jan-2012 |
Adam Cohen <adamcohen@google.com> |
Fix issue 5905210, AdapterViewAnimator sending negative index to Adapter
Change-Id: I6c1a3c17f1009d9512328f5844e17025f95a216c
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 0764dee89cc82dd53196cce2865d3cabafed208f |
|
18-Jan-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Merge "AccessibilityEvent/AccessibilityNodeInfo class name property should be set to only framework classes."
|
| b967392e0170af8cfd8053fd43fcdf8c46f703e9 |
|
05-Jan-2012 |
Adam Cohen <adamcohen@google.com> |
Hinting RemoteViewsAdapter as to which views are visible
-> This prevents collection widgets from flashing loading
views when they are updated with new content
Change-Id: I1241ff9a09edfd990ad03f76449d18b9359246b4
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 8a78fd4d9572dff95432fcc4ba0e87563415b728 |
|
17-Jan-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
AccessibilityEvent/AccessibilityNodeInfo class name property should be set to only framework classes.
AccessibilityEvent and AccessibilityNodeInfo have a property className which is set to the source
Java class. This is problematic since leads to leaking private classes which would allow an
accessibility service to load classes from other packages. This is strongly undesirable since
not trusted code can be loaded, and hence executed, in the accessibility service. To address
that the class name is set to the most concrete framework class extended by the info/event
source.
bug:5878943
Change-Id: I7b3114ece8772ea2773f5151e21b8a6f2006882a
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 2148d43eb23c702e834c93ae427f822f32d280a2 |
|
28-Jul-2011 |
Adam Cohen <adamcohen@google.com> |
Fixing widget notifyDataSetChanged() not getting called, issue 5092676
Change-Id: I61a034a77c0c9d07aba71bfabe7a0864ce92c2e9
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| d38a0cee2074fcf8005fc0d746aad282941a39b8 |
|
06-Apr-2011 |
Adam Cohen <adamcohen@google.com> |
Fixing AdapterViewAnimator onItemClick compatibility
Change-Id: I7b7c37370d0afdc23c62534ea41ffedc8f96f8ff
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 26f072c3ee4f2baecf4fd3f8ed829ed709055cf4 |
|
02-Apr-2011 |
Adam Cohen <adamcohen@google.com> |
Making StackView res-out and click feedback colors stylable
Change-Id: Ia6241b1b66dc510b22bcf342d775f98eb7c86871
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 0b96a57c851af2f66e3bc738035478efb3c1957e |
|
11-Feb-2011 |
Adam Cohen <adamcohen@google.com> |
Making AdapaterViewAnimator setDisplayedChild remotable
Change-Id: Idee91f457e1d4316feb077aaa949baa54eca6ab1
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 53838d265e36fb50341af168f5a91c3341c3cfc3 |
|
27-Jan-2011 |
Adam Cohen <adamcohen@google.com> |
Fixing some ugly StackView relayouts on rotation
Change-Id: Ic4b11637ed73e60e1af1fcd27e5610d8f84a31fe
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 2035a4657a900e25d5133ad0905105a70f2eedbb |
|
26-Jan-2011 |
Adam Cohen <adamcohen@google.com> |
Fixing bug where widgets would go dead after moving to another screen
-> A memory optimization was causing AdapterViewAnimator to give up its
reference to its adapter, rendering the widget dead.
-> Did testing, and it doesn't appear that this optimization was
making a difference, so it appears safe to remove.
Change-Id: I274c5f73862cbda2dc5411d5c94a9ba1ac1e3635
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 2c070bae4493cd1976c5086ec4cbf6ce10482742 |
|
26-Jan-2011 |
Winson Chung <winsonc@google.com> |
Merge "Re-enabling queued unbinding of services after requests to the service. (3394210)" into honeycomb
|
| 16c8d8a558f94ec14ef52bb5ac11044e2d0d902c |
|
21-Jan-2011 |
Winson Chung <winsonc@google.com> |
Re-enabling queued unbinding of services after requests to the service. (3394210)
- Fix for crash when detaching from window
- Potential fix for occasional IllegalStateException when updating List based widgets
Change-Id: I3d3f2bb691552a1136111043db686c4926b510c6
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 78db1aa9118edd71c2da28a2c23a0d875d1a707a |
|
25-Jan-2011 |
Adam Cohen <adamcohen@google.com> |
Cleaning up StackView
Change-Id: I38cd8a5f2d25973d3f97551be0a873ca35044ed9
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| e86ff4d56145d875c13a1637833f9f55d79febc9 |
|
22-Jan-2011 |
Adam Cohen <adamcohen@google.com> |
Fixing a couple StackView bugs:
-> Making sure to update visuals every time adapter count changes
-> Fixing a clipping issue seen on some devices
Change-Id: I489395b5caaa06eb7187b2dac679b793bf54d7e1
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| ef17dd497edc14ca753616862efaa3457e1df5da |
|
21-Jan-2011 |
Adam Cohen <adamcohen@google.com> |
Cleaning up some StackView bad behavior
-> Issue: 3363564, 3320865
Change-Id: I32215478006a689f543532af4ce2267ccbb7fa56
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 0e2de6d7187ef67ec00a2f2544450caa4a239c39 |
|
20-Jan-2011 |
Adam Cohen <adamcohen@google.com> |
Addressing API Review docs bugs:
->Issue 3370313
->Issue 3370403
->Issue 3370328
->kthx, bye
Change-Id: I2d1962c27b3ba856a0b4632d335271300bab45eb
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 69d66e00136f67332c992326a7b2eb334eeb32a2 |
|
12-Jan-2011 |
Adam Cohen <adamcohen@google.com> |
Fixing StackView rotation bugs
Change-Id: Iaf9482734ca73238f82d180700389593df9c7eac
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| ec84c3a189e4aa70aa6ea8ba712e5a4f260a153b |
|
14-Jan-2011 |
Patrick Dubroy <dubroy@google.com> |
Allow old view hierarchy to be GC'ed more quickly during rotation.
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| fb60386b46d0c6216c765c10bd33ac42ca780917 |
|
17-Dec-2010 |
Adam Cohen <adamcohen@google.com> |
Addressing issues associated RemoteViewsAdapter's service crashes / disconnects
-See issue: 3052667
Change-Id: I95f1cac3defeadc38ac75453d9d59cd1b3cbcc83
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 189ee18d6c6483ad63cc864267328259e2e00b95 |
|
03-Dec-2010 |
Dianne Hackborn <hackbod@google.com> |
Implement smarter sizing of WRAP_CONTENT windows.
This extends the view hierarchy's measure pass to allow view to
propagate up to their parent additional information besides just
their measured size. They can now report that their measured width
and/or height should be larger than the size their parent is
limiting them to (even though by definition they need to contrain
their reported measurements to the limits imposed by the parent).
ViewRoot uses this information to determine if it should remeasure
the window with a larger size limit to try to make it fit.
Change-Id: I90af3b7a8ec45d0a5c003fb009857025209d83eb
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 0ac116b688380489c3690f6f65b282990c221f17 |
|
11-Nov-2010 |
Adam Cohen <adamcohen@google.com> |
-Prevent StackView from advancing while interacting with it
-Fixed null pointer exception
Change-Id: I294a0d055de51573d79219ef469c8df6ab04a297
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| a02fdf1ba03fad71cc80a89dfc74b17456d5b4a5 |
|
03-Nov-2010 |
Adam Cohen <adamcohen@google.com> |
Adding widget auto-advance capability
Change-Id: I058573f40a48fd7b5c2efa5f1041a1199919a51a
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| a32edd4b4c894f4fb3d9fd7e9d5b80321df79e20 |
|
26-Oct-2010 |
Adam Cohen <adamcohen@google.com> |
Adding click feedback to widget collections
Change-Id: I97fceb6c68ca6eb1b703eafacf201e1aed7c38e7
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| a9238c89a43500ed0bcdeaee182be08ff991c627 |
|
25-Oct-2010 |
Adam Cohen <adamcohen@google.com> |
-> Fixing a bug where AdapterViewAnimator doesn't refresh correctly
-> Reduced swipe threshold for StackView
Change-Id: I0f04f45dade57f29581fe03fb195a6db5f12adb1
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 96d8d56302da81b24333b204e6d7f15064538036 |
|
24-Oct-2010 |
Adam Cohen <adamcohen@google.com> |
Fixing the case of less than or equal to 5 items in StackView
Change-Id: I9226fe8343902e06e2f4b04837e232f1744786a8
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 6f279627cfa3286e6901a8dc2ed8361576ce226d |
|
14-Oct-2010 |
Adam Cohen <adamcohen@google.com> |
Fixing null pointer exception
Change-Id: I902dfc9baa1be7fb07110ccde7a3c0e0049e4417
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 2794eb3b02e2404d453d3ad22a8a85a138130a07 |
|
13-Oct-2010 |
Chet Haase <chet@google.com> |
Remove generics from Animator APIs
Change the manner of constructing Animator-related objects from constructors
via generics to factory methods with type-specific method names. Should
improve the proliferation of warnings due to generics issues and make the
code more readable (less irrelevant angle brackets Floating around).
Change-Id: Ib59a7dd72a95d438022e409ddeac48853082b943
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 83d6e8213230fb0805aa019d266842253baeb114 |
|
14-Oct-2010 |
Romain Guy <romainguy@google.com> |
Revert "Remove generics from Animator APIs"
This reverts commit 41f041d9986f8a5d45b6cb0b86e881c81a412168.
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 41f041d9986f8a5d45b6cb0b86e881c81a412168 |
|
13-Oct-2010 |
Chet Haase <chet@google.com> |
Remove generics from Animator APIs
Change the manner of constructing Animator-related objects from constructors
via generics to factory methods with type-specific method names. Should
improve the proliferation of warnings due to generics issues and make the
code more readable (less irrelevant angle brackets Floating around).
Change-Id: I7c1776b15f3c9f245c09fb7de6dc005fdba58fe2
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 3042944c6ec68210ba1746540b53789e70d15ef4 |
|
06-Oct-2010 |
Adam Cohen <adamcohen@google.com> |
Fixing AdapterViewAnimator crash when associated adapter is empty
Change-Id: I3186452eb93f1141b06531507b13d87804e684d4
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| ef52176f1244a5bb98d82a0c8c7f4351edec17a1 |
|
04-Oct-2010 |
Adam Cohen <adamcohen@google.com> |
Changing AdapterViewAnimator to use the new animation APIs
Change-Id: Ifefb83c391914ac623d75e0faca723b95786861d
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 1b065cd1401253f999caa5d0ac12909407cef00e |
|
28-Sep-2010 |
Adam Cohen <adamcohen@google.com> |
Added looping parameter to AdapterViewAnimator / StackView
Change-Id: Iad36f7c0e657ffbae6dd17d0c9464ddf12de8b7b
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 6364f2bbe5254b4274f3feffc48f4259eacc205e |
|
29-Sep-2010 |
Winson Chung <winsonc@google.com> |
Fixing issue where notifyDataSetChanged was not properly being called while not loading items.
Change-Id: I46bb30a5a95576891f11873b214f5c760f5d1757
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 3ec9a45c36d3ca5ffbc6e85bbeb497b065e14155 |
|
24-Sep-2010 |
Winson Chung <winsonc@google.com> |
Re-architecting RemoteViewsAdapter internals due to new constraints.
- Respecting the AdapterView/Adapter contract using FrameLayout notification to update individual items
- Initial changes to allow for keeping (currently bitmap only) memory in check when loading numerous RemoteViews
- Fixing issue with leaking activities due to extra service connection references
- Fixing issue with multiple RemoteViewsAdapters being set on the same AdapterView
- Fixing small issue with StackView sometimes requesting indices out of bounds
- Removing background loading, reverting to previous message-queuing method (seems to be performant now)
Change-Id: I42313767aa791dfe35c247c97ae5d64389e6bb4c
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 9b3a2cf2a0a482ce8212eb2775176dd4c23e8e9a |
|
16-Sep-2010 |
Winson Chung <winsonc@google.com> |
Prevent multiple RemoteViewAdapters from being set for the same intent.
Fixing issue where we were comparing and storing intents incorrectly in the RemoteViewsService reference counting scheme.
Change-Id: Iedf5997ed3a3ee7f8729cf8689121913196571f8
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| dfcdddd7c408dddb22fb0867e4799d4c29d2f55f |
|
10-Sep-2010 |
Adam Cohen <adamcohen@google.com> |
-> Fixing some layout issues in StackView
-> Made the highlight width depend on the screen density
Change-Id: I6b3ae68de5fb90728938a7e0869cf97e816aa6af
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| bd0136a2fde1d81a835f94efe3193569b10d99ff |
|
08-Sep-2010 |
Adam Cohen <adamcohen@google.com> |
AdapterViewAnimator now properly handles notifyDataSetChanged
Change-Id: Icc22671b76d49c4229f118f77a5c269253a07b84
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| a18a86b43e40e3c15dcca0ae0148d641be9b25fe |
|
07-Sep-2010 |
Chet Haase <chet@google.com> |
Rename several animation classes
Change-Id: I6a4544875090db485163c8d56de8718f56d267c7
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 839f4a54e5a6fe602dbc5998b01412d809eba722 |
|
27-Aug-2010 |
Adam Cohen <adamcohen@google.com> |
-> Implemented new visualization for StackView
-> Cleaning up the method for creating the blue outline
-> Reimplmented onMeasure for StackView and AdapterViewAnimator
Change-Id: I59ce063661d59412de05d1a471644674f83bb7d1
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 1480fddea874a42adb43b4bcdac6704e4c3e110b |
|
26-Aug-2010 |
Adam Cohen <adamcohen@google.com> |
-> Added the ability to specify an AdapterView's empty view
through RemoteViews. An empty view is the view that appears
in lieu of the collection when the collection is empty.
-> Made StackViews start at their last item
Change-Id: Ica44e5e8f8f2a2e5589a6c74414ec4d08303887f
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 9b073948cfb84c0dd04f8a94ee1f7f263f027c83 |
|
20-Aug-2010 |
Adam Cohen <adamcohen@google.com> |
Cleanup and bug fixes in StackView
-> pushed functionality from AdapterViewAnimator to StackView
-> only modifying clipping flags as far up the view
hierarchy as needed
-> still need framework level solution for drawing outside bounds
ViewGroup touch dispatch temp fix
-> Touch event was being modified and not reset in some
code paths.
Change-Id: I8135b62e2d73f239b9df407b0fa93bc434796989
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 3d07af03421f4727ef7e97c5c19e6ade50b19060 |
|
19-Aug-2010 |
Adam Cohen <adamcohen@google.com> |
-> Added edge behaviour for StackView (what to do at
the beginning and end of the stack)
-> Wrapping children of AdapterViewAnimator in a
FrameLayout to uphold the Adapter contract (ie.
don't modify the Adapter's views.)
-> Fixed clipping problem in StackViews with padding
Change-Id: I83b02b5fdfd687838346e0bcb5dc30c033cd0cb8
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| b04f7ad90b7d5d5e0998e3b56960004cf56e6e8f |
|
15-Aug-2010 |
Adam Cohen <adamcohen@google.com> |
-> Added 3D rotation to the StackView transition
-> Fixed a bug with multiple animations occuring at the same time
-> Added looping paramater to AdapterViewAnimator
-> Added restoration of state to AdapterViewAnimator
-> Fixed a flicker in the default AdapterViewAnimator transition
(could be seen in AdapterViewFlipper)
-> Fixed a bug where touch events of StackView weren't be
propagated to the proper child
Change-Id: I270280cabc42ad77d28e3e7d7d80aa4c17548cab
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 5b53f9186e7812c93bc578d18e92cb123481fcbc |
|
17-Aug-2010 |
Romain Guy <romainguy@google.com> |
Fix possible ClassCastException in StackView.
Also do some cleanup (unused arguments, unnecessary casts, etc.)
Change-Id: If1f8cc173ca6fee33c54f4437bc5dcdbc75e5947
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 32a42f1587db77b958d62c3de4f2734eb0a3b965 |
|
12-Aug-2010 |
Adam Cohen <adamcohen@google.com> |
-> Refactored and cleaned up dragging / animations
-> Added methods to generate blue glow outline
-> Added "res-out" effect
-> Added some influence for dragging left / right
Change-Id: I4bdbe4c3bd843ed5616b1ea359a3b0af1c151814
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 8322834a2544a673a35c5d4ad0d5909b3ca37600 |
|
11-Aug-2010 |
Adam Cohen <adamcohen@google.com> |
Fixing StackView crash associated with DataSetObserver
Change-Id: Idbc8ed09ee8a58757b7383d6331a4c0357a6fb1f
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 44729e3d1c01265858eec566c7b7c676c46a7916 |
|
23-Jul-2010 |
Adam Cohen <adamcohen@google.com> |
Preliminary implementation of StackView, which extends AdapterViewAnimator.
Change-Id: I3e9d1203fc8848835f28d6bc1c9dc0a3fcf7f242
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|
| 3db40678d33c2b5f90c380966d36b3e10ed11f05 |
|
20-Jul-2010 |
Adam Cohen <adamcohen@google.com> |
Added AdapterViewAnimator and AdapterViewFlipper which are versions of ViewAnimator and ViewFlipper
whos views are defined by adapters.
Change-Id: I6ca1681b4820e6a1b6b69fc6d92c11c9f969bb88
/frameworks/base/core/java/android/widget/AdapterViewAnimator.java
|