| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
Change-Id: I8e88c399c2b0dcba9f65d1bcf89fdddf432e4ed6
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* commit 'ce57a7f35344e76689d30f45964d1e37b78280cb':
GpsLocationProvider: Clean up HAL initialization/cleanup sequence
Fixed GSM encoded network initiated position request
Ensuring thread-safe usage of DateFormat.
Fixing infinite loop for zero duration.
Fix for an infinite loop while scrolling lists.
WAPPushManager, WAP Push over SMS message handler
Add --non-constant-id to aapt.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When scrolling in a list it's possible to get stuck in a
loop where the screen is continuously redrawn. This happens
when you are at the end of a list and try to scroll further.
The problem is that you enter a switch statement with the
mState variable set to STATE_PULL_DECAY. This will trigger
code in the switch statement that does some adjustments and
calculations, but it does not change the value of mState to
STATE_IDLE or STATE_RECEDE after it's done. Hence it will
continue to return to the same place and not stop updating
since the update() method signals for completion only when
the mState variable is set to STATE_IDLE.
The fix is changing the value of mState after the
adjustments and calculations have been made.
Change-Id: I57bc84ec12d43ca87a1163d94cb5b206a376a24e
|
| | |
| |
| |
| |
| |
| |
| | |
The decay is now in line for the decay for absorb glows.
Fixes b/3094064 Overscroll fade timeout is too long
Change-Id: Ida987c8f6193fcb15f743d72c590a5c1daef056d
|
| | |
| |
| |
| |
| |
| |
| |
| | |
No matter how much the user drags, the alpha like the height
should not get greater than a max and that max is 80% of what
is available in the image.
Change-Id: I57d181d6ea685461a44ed3ee29f83a675bc07fbc
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Event when the user keeps pulling, should NEVER get bigger than
the max height (~2list items tall).
Fixes b/3074337 Overscroll glow can be stretched indefinitely
Change-Id: Ifc30d4c907d432faf9ee10ddc20bcc8f50b21f81
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Edge decay is now based on the remaining height of the glow so that
as the glow reduces, the edge will reduce and not disappear entirely
before the glow is gone.
Change-Id: I03376ee3807e21ce6ac74c0cfad713b7fd5e4520
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The issue here was originally that webview was showing twice
as intense of an effect for edge glow as lists. The root cause
was that abslistview was calling onPull half as often as webview. This
occurred because every time an action_move came into the touch handler
for abslistview when it was in overscroll, the mode was ALWAYS changed
back to scroll mode. Therefore, half the action_move events were
essentially being eating by the abslistview state machine.
After fixing that issue, needed to decrease the intensity of the effect
for webview and abslistview by halving the PULL_DISTANCE_GLOW_FACTOR.
Change-Id: I5dbdf4f1219f3bb157a71d4fccf8fa42e2abe047
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Change-Id: I7864dd4d3e15a9dc11429d5d3268f9b078f3eaad
Constants updated to match user testing.
Recede no longer flashes out but degrades all the way to zero.
Growth of the absorb flash is now quadratic as this better
matches the "physics" of the user flicking the list.
Size of the pull and absorb graphics changed to give the user
a more dramatic indication of what has happened.
|
| | |
| |
| |
| | |
Change-Id: I367643877a397e7b4fa9bd8c40639ff69436e7f0
|
| | |
| |
| |
| |
| |
| | |
TODO Effect for scaling gestures; asset/polish tweaks.
Change-Id: Ifbc201cb64e0610dbc92a7c57ba0d3a4ee686c43
|
| |
|
|
|
|
|
|
| |
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 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
|
| |
|
|
| |
Change-Id: Id2ad0ff4fa78617cb79475952e9ce561ee8fec10
|
|
|
Change-Id: I3eb4413261b38ddd8c609d6153bdfd4ae46c6a0f
|