| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
Change-Id: I0e4bf09c0cbc660c9b8d26a3526b09568c05e93d
|
| |
| |
| |
| | |
Change-Id: I367643877a397e7b4fa9bd8c40639ff69436e7f0
|
| |
| |
| |
| |
| |
| |
| |
| | |
TODO: Currently disabled for WebView. Assets used for the glow effect
need to be themable/styleable. Overscroll effect should take place
even when the user did not grab the widget within actual content.
Change-Id: I68277d14d37dc5bcdb9254eaddf6e4998b3f2bf4
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
New pointers touching the screen always become the active pointer.
Still to do: allow flings until another pointer moves enough to stop
it. Currently flings will be immediately stopped by the other pointers
still contacting the screen.
Change-Id: Ic1c7bf98dcf40252593cec0ab1f0d524aaeed8e4
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Dispatch ACTION_HOVER_MOVE and ACTION_SCROLL through the View
hierarchy as onGenericTouchEvent. Pointer events dispatched
this way are delivered to the view under the pointer. Non-pointer
events continue to be delivered to the focused view.
Added scroll wheel support to AbsListView, ScrollView,
HorizontalScrollView and WebView. Shift+VSCROLL is translated
to HSCROLL as appropriate.
Added logging of new pointer events in PointerLocationView.
Fixed a problem in EventHub when a USB device is removed that
resulted in a long stream of ENODEV errors being logged until INotify
noticed the device was gone.
Note that the new events are not supported by wallpapers at this time
because the wallpaper engine only delivers touch events.
Make all mouse buttons behave identically. (Effectively we only
support one button.)
Change-Id: I9ab445ffb63c813fcb07db6693987b02475f3756
|
| |
| |
| |
| | |
Change-Id: Ia110f30279a93c96741e9afbd93ed6231aa97ef1
|
| |
| |
| |
| | |
Change-Id: I3c6513ada6bdd192c83f3ff59a2c85717156de22
|
| |
| |
| |
| | |
Change-Id: I09d99290ca74f96046702bc2604f125a1276ce05
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, display lists were used only if hardware acceleration
was enabled for an application (hardwareAccelerated=true) *and* if
setDrawingCacheEnabled(true) was called. This change makes the framework
use display lists for all views in an application if hardware acceleration
is enabled.
In addition, display list renderering has been optimized so that
any view's recreation of its own display list (which is necessary whenever
the visuals of that view change) will not cause any other display list
in its parent hierarchy to change. Instead, when there are any visual
changes in the hierarchy, only those views which need to have new
display list content will recreate their display lists.
This optimization works by caching display list references in each
parent display list (so the container of some child will refer to its
child's display list by a reference to the child's display list). Then when
a view needs to recreate its display list, it will do so inside the same
display list object. This will cause the content to get refreshed, but not
the reference to that content. Then when the view hierarchy is redrawn,
it will automatically pick up the new content from the old reference.
This optimization will not necessarily improve performance when applications
need to update the entire view hierarchy or redraw the entire screen, but it does
show significant improvements when redrawing only a portion of the screen,
especially when the regions that are not refreshed are complex and time-
consuming to redraw.
Change-Id: I68d21cac6a224a05703070ec85253220cb001eb4
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes a regression from Froyo. Previously, when a scroll view
had no children, its onTouchEvent would return because the scroll
view would only start dragging if the user touched one of its children.
In Gingerbread, the user can drag from anywhere within the scroll
view, not just by touching a child. However, it makes no sense
to drag a scroll view that has no children so an empty scroll view
should just ignore touches like any other empty view group would.
This change fixes applications that for some reason or other happen
to have empty scroll views in strange places.
Bug: 3246230
Change-Id: Iada6e886e8363e6778f42fc4861de228512d8bed
|
| |
| |
| |
| |
| |
| | |
Bug #3328711
Change-Id: Ic131f2feecbeec4a7250d47193c9794aa70d22ee
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Bug #3259668
If a FrameLayout is measured with an UNSPECIFIED or AT_MOST spec,
it cannot correctly define the size of its children set to
match_parent. This change adds a second measurement pass similar
to what LinearLayout does in the same situation.
Change-Id: I20ac5203c2efc2e559f88b2c9573d4ad7df488b4
|
| |
| |
| |
| |
| |
| |
| |
| | |
Instead of going past the left and right sides, the glow now
stretches just to the width of the edge and stops.
For horizontalscrollview, instead of going past the top and bottom,
now stretches just to the height and stops.
Change-Id: I0cc9bdef3ab263b16dd32e088c6b64ff5a8809c8
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
New algo is:
1) if view width < MIN_WIDTH (currently 300px), clip glow and edge to fit
2) else stretch glow and edge to fill width
3) make alpha and height of edge and glow 30% "more intense"
Change-Id: I8f121bb165a8fb835bc33950dbedd1bc80c5df65
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Between the animation system, ListView, and this, we can now account
for the large majority of animations in-flight at any point and annotate
StrictMode violations accordingly.
Note that StrictMode.Span goes out of its way to not allocate memory
and is very light-weight, especially on user builds where it's a
no-op.
I've tested this with the LOG_V debugging in StrictMode and I think
I've gotten all the entry/exit cases of ScrollView's animations. At
least, I'm not able to get it out-of-sync at least, even with
orientation changes during scroll/fling, etc. It's possible I missed
a path, but that should show up as excessive false positives during
dropbox uploads if so.
Change-Id: I3b0545111a775d9fa8e171f2a190031f1b56c4c0
|
| |
| |
| |
| | |
Change-Id: I3eb4413261b38ddd8c609d6153bdfd4ae46c6a0f
|
|/
|
|
| |
Change-Id: I34f5418ca33933dc5cf65f4e417d918bce83ab96
|
|
|
|
|
|
|
|
| |
Bug #2581646
The correct fix is to make ScrollView ignore the BACK key instead of consuming it.
Change-Id: I5c029a5c60ae8e7791391f63672c44b5c96fec71
|
|
|
|
| |
Change-Id: I551803a1c997c9d10e1d004ce14472af6090f432
|
|
|
|
| |
Change-Id: I7e9db8d8a9b8ef67f0c0c82bf57c9155b7ebabea
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Plugged a possible edge case with ScrollView/HorizontalScrollView that
could cause this error.
Change-Id: I509004189b9f5e536d6213c9fdfff598d9f958ca
|
|
|
|
|
|
|
| |
Awaken scroll bars in onOverscrolled instead of based on the timing
reported by the Scroller's animation.
Change-Id: I8510b92b9fdf471fc8d6f8f089681eb23d10f190
|
|
|
|
|
|
|
|
|
| |
OverScroller has been made a Scroller child class. Both use a physical constant deceleration
force to compute the animation. OverScroller also includes a rubber edge bounce effect.
Approved by Jim Palmer.
Change-Id: I3f43a03694b8cb6bfa0784c2663b37c9c39322cc
|
|
|
|
| |
Change-Id: I434ec3edd95a19677ad9dbd1ac5ca3f3f5d091cb
|
|
|
|
|
|
|
|
| |
Bug #2342763
Also fix typos in TextView.
Change-Id: I58ab906b9bebe562c1a913977e2d6970bfcf3788
|
|
|
|
| |
AbsListView multitouch scroll and only grip on content
|
|
|
|
| |
wouldn't scroll if the initially tapped child ignores the down event.
|
| |
|
| |
|
|
|
|
|
|
|
| |
scroll content out of view. Scrolling will slow down halfway to the
barrier point. API added in View. AbsListView, ScrollView,
HorizontalScrollView all use this API. Overscrolling uses haptic
feedback. Added scroll barrier pattern to config.xml.
|
| |
|
|
|
|
| |
scrolls out of bounds. Tweaked bounce physics for OverScroller.
|
|
|
|
| |
HorizontalScrollView.
|
|
|
|
|
|
|
|
| |
If a touch event was targeted at a ScrollView child, the content would jump after
the user moved her finger by the required threshold. This is inconsistent with
ListView's behavior.
Fixes #2296622.
|
| |
|
|
|
|
| |
keyboard.
|
|
|
|
| |
Add several checks to make sure there's at least one child.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|