Not closing the cursors was a bit of a bug since the documenation explicitly says that it would close the cursors. This will get rid of all the warnings that are printed out in the finalizer about the cursor not being closed.
Merge commit '7e5e3745cf0103219a13071fbd488c3c01da85d9' into froyo-plus-aosp
* commit '7e5e3745cf0103219a13071fbd488c3c01da85d9':
Fix bug 2710825 - Prevent ExpandableListView from scrolling too far when expanding children.
When showing a progress bar instance more than once
it will not animate after the first time.
Change-Id: I5104c551d561755005e533f2ab5257454567bf71
Signed-off-by: David Sobreira Marques <dpsmarques@gmail.com>
During onRestoreInstanceState for DatePicker, the internal
state of the widget is restored properly (thus setting the
internal year, month, and day), but the spinners aren't
visually updated to that state immediately. That is to say,
the internal state of the widget doesn't match the spinners
in that case, which can cause confusion.
Change-Id: I96d1a299d0ee159d41450470acb30a3bf6006d44
The problem appears when the user selects, copies and paste text
and then selects text again. The second time text is selected,
the copied text becomes visible in the text field.
Change-Id: Iae19d1659f58ad2e1c6f1a98bdef8bbedabd447f
Allow the user to start scrolling back into content immediately
after dragging past the end of content.
Remove some dead code.
Change-Id: Ife8f60499ac58179ba1e2500ca8745916392a4bc
AbsListView was relying on TOUCH_MODE_DOWN to signal that the item was
enabled, but onInterceptTouchEvent uses it for other purposes. Check
before dispatching the event.
Change-Id: I6babd3872cb51ebdba8e97a3b349e0cc08cd1279
OverScroller is no longer a child class of Scroller and several
Scroller methods that do not make sense for OverScroller and could
cause misbehaving edge cases have been removed or hidden and
deprecated.
Change-Id: Ie055b607bd3b36c47ab9798d5c9518aef686b474
The view infos should never be null since they are created by ListView, which is
the natural and only use of this class.
However, some tests in CTS pass null pointers. Replace null by a static empty list.
http://b/issue?id=2527753
Change-Id: I9b92fa018c89007f12be899285f75130b2c8ac40
Null header and footer, as used by CTS tests, were no longer supported.
Added a static empty list to avoid repetitive null tests in that case.
Fixed getItem/getItemId/getView to handle corner cases.
Changed ListAdapter isEnabled documentation for invalid positions.
http://b/issue?id=2527753
Change-Id: I55e5bf21cb0673d906caa7c669987a6ae869d90f
Handle ACTION_CANCEL, fix edge cases related to grabbing content and
beginning a new scroll during overfling/springback. Will prevent
some cases where a view could get stuck overscrolled.
Change-Id: I7e89d9de9b7dc685d2ea278e6b2bd2c794364204
Awaken scroll bars in onOverscrolled instead of based on the timing
reported by the Scroller's animation.
Change-Id: I8510b92b9fdf471fc8d6f8f089681eb23d10f190
AutoCompleteTextView now uses different logic to expand the dropdown
list of completion choices to cover the IME if present. Previously
this would happen whenever a touch down event occurred. Resizing the
dropdown could cause the parent view to animate a scroll and thereby
move the completion list up the screen. When this happened with a
finger down it would initiate a touch scroll on the completion
list. Prior to froyo this wasn't a problem since a list positioned at
the top could not scroll up, but with the addition of overscroll this
caused undesired behavior.
The completion list now will not expand to cover the IME on initial
touch down. Instead it will only expand if the user leaves a finger in
place for the duration of a timeout (currently 250ms) or if the user
explicitly begins a touch scroll on the completion list. This also has
a nice side effect where tapping a completion choice in the initial,
smaller list does not cause a split-second list expansion before the
list is dismissed.
Change-Id: If0994c68a91b3bfc3dcef660c67fde667a9727f9
Bug http://code.google.com/p/android/issues/detail?id=7251
Previously, a spinner using checkable list items would try to bind data as booleans
instead of text. This change takes this use case into account.
Change-Id: Ie4ced01e3c0235138e1dd68426d6a748c2843a9c
The constant force that was applied has been replaced by a spring force
when the OverScroller goes beyond valid position values.
Bounce coefficient can be set for each directions.
Change-Id: If7d506d3f35b3451f590c54d6c04a1deb8d9ca95
