77e9a28e2faa36f127231b842476d47f9823a83a |
|
13-Sep-2013 |
Alan Viverette <alanv@google.com> |
Add live region politeness to View, AccessibilityNodeInfo Alters the content change API to contain a bit mask of types of changes represented by the event. Live regions send CONTENT_CHANGED events immediately. Removes unused APIs for EXPANDABLE/EXPANDED. BUG: 10527284 Change-Id: I21523e85e47df23706976dc0a8bf615f83072c04
/frameworks/base/core/java/android/widget/CompoundButton.java
|
7df754e7121253a4b6e48d19a213cbf5aac458be |
|
10-Jul-2013 |
Chet Haase <chet@google.com> |
Remove unnecessary drawable code in CompoundButton Some of the code in setButtonDrawable() was unnecessary, resetting the button drawable state and then refreshing it. This caused many redundant calls, which can add up, especially during inflation. Change-Id: I873cf5eef697b5435a1b827cd68e5d836ee25124
/frameworks/base/core/java/android/widget/CompoundButton.java
|
6254f4806dd3db53b7380e77fbb183065685573e |
|
05-Jun-2013 |
Svetoslav <svetoslavganov@google.com> |
Optimizing AccessibilityNodeInfo caching. 1. Before we were firing an accessibility event from the common predecessor of views with accessibility related state changes every X amount of time. These events designate that the tree rooted at the source is invalid and should not be cached. However, some of the state changes do not affect the view tree structure and we can just refresh the node instead of evicting and recaching nodes infos for views that did not change. Hence, we need a way to distinguish between a subtree changed over a node changed. Adding a new event type will not work since if say two siblings have local changes and their predecessor fires a window state change event, the client will drop the subtree rooted at the parent including the two views with changes. Subsequent, more specialized events emitted from the two changed siblings will be useless since the parent which did not changed is already evicted from the cache. Conversely, if the specialized events are fired from the two siblings with local changes and they are refreshed in the cache the subsequent window state change event from the common predecessor will force the refreshed nodes to be evicted. Hence, to enable distinction between node being changed and a subtree baing changed while not changing existing behavior, we will fire only window content change event with an additional argument specifying what changed - node or a subtree for now. Also if the changes are local to a view we fire the window content changed event from the view. So, the two siblings will fire such an event independently and the client will know that these are local changes and can just refresh the node. If the changes are structural, then we fire the window state change event from the common predecessor. 2. Added the input type of a text view as one of the properties reported by an AccessibilityNodeInfo. It is nice to prompt the user what input is expected. 3. Added a bundle for optional information to AccessiiblityNodeInfo. For example, it will be used for putting web specific properties that do not map cleanly to Android specific ones in WebView. 4. AccessibilityInteractionController was not taking into account whether the current accessibility focused node is shown before returing it. Hence, a disconnected node would be returned and caching it puts our cahche in an inconsistent state. Change-Id: I8ed19cfb4a70bdd7597c3f105487f1651cffd9e0
/frameworks/base/core/java/android/widget/CompoundButton.java
|
b878ddb56ec4e755706890110d76735176ff2295 |
|
28-Nov-2012 |
Fabrice Di Meglio <fdimeglio@google.com> |
Fix bug #7621927 Radio button/TextView drawable regression in 4.2 - as we remove the 9 patch padding trick, we need also to do the correct positioning of the radio / checkbox / star during draw Change-Id: I02b67bef9c0f2dc1c0c65361de14ab20ce9b881d
/frameworks/base/core/java/android/widget/CompoundButton.java
|
2842679d3426295b6674dfcfb8591fad79de6cb2 |
|
06-Jun-2012 |
Fabrice Di Meglio <fdimeglio@google.com> |
Make CheckBox / RadioButton / ToggleButton / Star widgets aware of layout direction - see bug #5429822 UI should be mirrored for RTL locales (Arabic, Hebrew, farsi) Change-Id: I8badb57d095c6a0a1d0c82bedf30b02502013ae0
/frameworks/base/core/java/android/widget/CompoundButton.java
|
c406be9036643ebe41bafcd94fe4aa861b4e4f4f |
|
12-May-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Fix inconsitency in aAccessibilityNodeInfo cache. 1. Fixed errors in the accessibility node cache. A. The cache was not catching the case when the current window changes as a result the user touch exploring it. As a result the cache had nodes from more that one window but the node ids are not unique thus causing a mess. B. The node info tree was prefetched regardless if a prefetched node is root name space (i.e. view ids - not accessibility ids - are namespaced) while the prefetched nodes were taking this into account. As a result there can get disconnected subtrees in the cache. C. When an event for a property change such as focus was received the cache we were removing the source node. As a result there may be disconnected nodes. D. When a node was added to the cache and an older version exists there was no check if it will point to the same children and parent. As a result if the state of the node has fewer children the subtrees rooted at the no longer present children will stay disconnected in the cache. E. When a node got accessibility or input focus the old one in the cache was not removed. As a result you may have a state with more than one access or input focus. 2. Added integrity check enabled only on user builds when a specific flag is set for the cache which checks whether: A. All nodes are from the same window. B. All nodes are connected. C. There are no duplicates. D. There is only one input focus. E. There is only one accessibility focus. 3. The reported accessibility node info tree was stopping at the root namespace boundary which is not correct. The reported tree has to reflect everything on the screen that the user can see such a workspace with widgets. The root namespace is added to avoid clash of view id but the accessibility ids are unique no matter if the view is inflated from a remote view. 4. Added calls to notify the accessibility layer when a preoprty that is interesting for accessibiliy has changed. bug:6471710 Change-Id: I069470d91f209ba16313fa6539787a55efa3512e
/frameworks/base/core/java/android/widget/CompoundButton.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/CompoundButton.java
|
0f55cc33f658b2793a12d609a0989348077324a4 |
|
17-Jul-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
AccessibilityNodeInfo does not report checkable coreclty. 1. AccessibilitiyNodeInfo's checkable property was not set. bug:5039205 Change-Id: I083d1c357c6d9875536e66e355c8a33bd580cee6
/frameworks/base/core/java/android/widget/CompoundButton.java
|
13774d2e38e73ef4d0f6d0db3501ba032fa6da5a |
|
16-Jun-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
AccessibilityNodeInfo not properly returning checked status 1. CompundButton was not setting its checked state in the info. bug:4674048 Change-Id: Ic711d4ee9b2214e9bdf86546df406b497aaa90b5
/frameworks/base/core/java/android/widget/CompoundButton.java
|
30401328c1026389171d454c934c15875c3f7ff0 |
|
13-May-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Factored out the Accessibility vertical initialization. 1. Accessibility events were filled with data in dispatchPopulateAccessibilityEvent and onPopulateAccessibilityEvent. These events have two axis of population 1) up the class hierarchy to populate information for the event source; 2) down the view hierarchy to populated all the text contained in the source including its descendants. These two axis of population were done in on population pass now the populating the source properties happens in initializeAccessiblityEvent and the text in onPopulateAccessibilityEvent which is called from dispatchPopulateAccessiblityEvent. 2. Removed the string description from events fired from CompoundButton since the event has isChecked() property and it is responsibility of the clients to decide what utterrance to use and if to use such for announcing the checked state. Change-Id: I5d7f75cf8a87a7a4b3bb7b311e8e642ec9a0faa5
/frameworks/base/core/java/android/widget/CompoundButton.java
|
736c2756bf3c14ae9fef7255c119057f7a2be1ed |
|
23-Apr-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Touch exploration feature, event bubling, refactor 1. Added an Input Filter that interprets the touch screen motion events to perfrom accessibility exploration. One finger explores. Tapping within a given time and distance slop on the last exlopred location does click and long press, respectively. Two fingers close and in the same diretion drag. Multiple finglers or two fingers in different directions or two fingers too far away are delegated to the view hierarchy. Non moving fingers "accidentally grabbed the device for the scrren" are ignored. 2. Added accessibility events for hover enter, hover exit, touch exoloration gesture start, and end. Accessibility hover events are fired by the hover pipeline. An accessibility event is dispatched up the view tree and the topmost view fires it. Thus predecessors can augment the fired event. An accessibility event has several records and a predecessor can optionally modify, delete, and add such to the event. 3. Added onPopulateAccessibilityEvent and refactored the existing accessibility code to use it. 4. Added API for querying the currently enabled accessibility services by feedback type. Change-Id: Iea2258c07ffae9491071825d966dc453b07e5134
/frameworks/base/core/java/android/widget/CompoundButton.java
|
3fb3d7c4e756bd32d5abde0abca9ab52d559bc84 |
|
23-Apr-2011 |
Adam Powell <adamp@google.com> |
Revert "Touch exploration feature, event bubling, refactor" This reverts commit ac84d3ba81f08036308b17e1ab919e43987a3df5. There seems to be a problem with this API change. Reverting for now to fix the build. Change-Id: Ifa7426b080651b59afbcec2d3ede09a3ec49644c
/frameworks/base/core/java/android/widget/CompoundButton.java
|
ac84d3ba81f08036308b17e1ab919e43987a3df5 |
|
05-Apr-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Touch exploration feature, event bubling, refactor 1. Added an Input Filter that interprets the touch screen motion events to perfrom accessibility exploration. One finger explores. Tapping within a given time and distance slop on the last exlopred location does click and long press, respectively. Two fingers close and in the same diretion drag. Multiple finglers or two fingers in different directions or two fingers too far away are delegated to the view hierarchy. Non moving fingers "accidentally grabbed the device for the scrren" are ignored. 2. Added accessibility events for hover enter, hover exit, touch exoloration gesture start, and end. Accessibility hover events are fired by the hover pipeline. An accessibility event is dispatched up the view tree and the topmost view fires it. Thus predecessors can augment the fired event. An accessibility event has several records and a predecessor can optionally modify, delete, and add such to the event. 3. Added onPopulateAccessibilityEvent and refactored the existing accessibility code to use it. 4. Added API for querying the currently enabled accessibility services by feedback type. Change-Id: Iec03c6c3fe298de3f14cb6efdbb9b198cd531a0c
/frameworks/base/core/java/android/widget/CompoundButton.java
|
e213677037f836529efcc0ac201fc61dd95481c5 |
|
04-Nov-2010 |
Dianne Hackborn <hackbod@google.com> |
Push the jumpDrawablesToCurrentState() thing off everywhere it should be. Also add a new interface that items in AbsListView can implement to adjust the bounds of the selection shown for them. This will allow contacts to use list view's regular selection facility rather than implementing something special in their item views. Change-Id: I29cbdbc7122111ee97e47fe7d6ec55ff07be79cc
/frameworks/base/core/java/android/widget/CompoundButton.java
|
7a36788f4a69b3ddaf8fb8e250e1a13bee7238fa |
|
24-Feb-2010 |
Steve Zeigler <sfzeigler@gmail.com> |
These changes add access to some status values in widgets listed below: widget/CheckedTextView.java: report if the item is checked or not. widget/CompoundButton.java: report if the item is checked or not. widget/ProgressBar.java: isIndeterminate(), getProgress(), getSecondaryProgress(), and getMax() report what sliders and progress bars are showing widget/TextView.java: report the current selection: getSelectionStart() and getSelectionEnd()
/frameworks/base/core/java/android/widget/CompoundButton.java
|
cf4550c3198d6b3d92cdc52707fe70d7cc0caa9f |
|
21-Jul-2009 |
Jean-Baptiste Queru <jbq@google.com> |
donut snapshot
/frameworks/base/core/java/android/widget/CompoundButton.java
|
9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/widget/CompoundButton.java
|
d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/widget/CompoundButton.java
|
d24b8183b93e781080b2c16c487e60d51c12da31 |
|
11-Feb-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@130745
/frameworks/base/core/java/android/widget/CompoundButton.java
|
54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/widget/CompoundButton.java
|