| 98365d7663cbd82979a5700faf0050220b01084d |
|
20-Aug-2012 |
Jeff Brown <jeffbrown@google.com> |
Refactor for multi-display support.
Split WindowManagerImpl into two parts, the WindowManager
interface implementation remains where it is but the global
communications with the window manager are now handled by
the WindowManagerGlobal class. This change greatly simplifies
the challenge of having separate WindowManager instances
for each Context.
Removed WindowManagerImpl.getDefault(). This represents the
bulk of this change. Most of the usages of this method were
either to perform global functions (now handled by WindowManagerGlobal)
or to obtain the default display (now handled by DisplayManager).
Explicitly associate each new window with a display and make
the Display object available to the View hierarchy.
Add stubs for some new display manager API features.
Start to split apart the concepts of display id and layer stack.
since they operate at different layers of abstraction.
While it's true that each logical display uniquely corresponds to a
surface flinger layer stack, it is not necessarily the case that
they must use the same ids. Added Display.getLayerStack()
and started using it in places where it was relatively easy to do.
Change-Id: I29ed909114dec86807c4d3a5059c3fa0358bea61
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| a8b9defade5b937d4ad64f9aff4bca792298f43c |
|
23-Jul-2012 |
Jeff Brown <jeffbrown@google.com> |
Stop using raw display size except in window manager.
We don't actually need the raw size in these places.
The logical size is good enough.
Starting to move dependencies on surface flinger
and window manager out of the Display class.
Change-Id: I2065bee8e5bf7f42c5a452dd1e8479e40ebb0d37
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| f877308f77f7c6f3edd91618a092207dd3be9077 |
|
13-Jul-2012 |
Romain Guy <romainguy@google.com> |
Remove obsolete optimization
Change-Id: I2d43c009c62a7f4a4a2e0a6303bdfa692c4b8c8c
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| e15ccb93add99ebb9cd7aec03a04faa37f45b39d |
|
17-May-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Changing the interaction model of the touch explorer.
1. Now the user have to double tap to activate the last
item. If the last touched window is not active because
it does not take input focus the click on the last
touch explored location. Othewise the click is on the
accessibility focus location.
bug:5932640
Change-Id: Ibb7b97262a7c5f2f94abef429e02790fdc91a8dd
/frameworks/base/core/java/android/view/ViewConfiguration.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/view/ViewConfiguration.java
|
| f87d19621dc2a30232bba1f51862a0b671eb9729 |
|
04-Apr-2012 |
Dianne Hackborn <hackbod@google.com> |
Clean up status bar, system bar, navigation bar management.
The status bar and navigation bar are two completely separate
elements, with their own semantics. The system bar now classifies
itself as a navigation bar, since that is really how it behaves.
This required rewriting the HDMI resizing code, so that it is
all done by PhoneWindowManager since that is what is responsible
for the size of the navigation bar (and thus now system bar). This
actually gets rid of a fair amount of code, and means we can also
do the same thing for a pure navigation bar.
Likewise the system bar now has the navigation bar ability to be
hidden when requested by system UI flags. To get the behavior
we want on Xoom, we only allow the nav bar to be hidden when it
will help provide a better aspect ratio for showing widescreen
videos.
Finally the nav/system bar now animates when hidden and shown.
Change-Id: Ie927154b68376a0b61802f99171ff56b8da92e7a
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| c19895f7ede3129d88728844940c2586c88e74b2 |
|
03-Apr-2012 |
Daisuke Miyakawa <dmiyakawa@google.com> |
Shorten PRESSED_STATE_DURATION
Bug: 6259150
Change-Id: Ic8b28295a7e97ca2885d074962f73d5f1bf980c6
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 887c2eea31a9ef2bc27186773e173e083eee7314 |
|
10-Mar-2012 |
Romain Guy <romainguy@google.com> |
Use the actual screen size for the max bitmap cache size.
Change-Id: I2177f91aea7c449c377fde6337180d15487cecef
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 243657993c0280771e07a3367d1a7ed45dbfe15f |
|
08-Dec-2011 |
Adam Powell <adamp@google.com> |
resolved conflicts for merge of db81dc72 to master
Change-Id: Ie7e1d9a255934e45d8b241b15e9674046cff2444
|
| 6720a87ad161a12c9dc7e11b2ae0165e65483464 |
|
08-Dec-2011 |
Adam Powell <adamp@google.com> |
Raise touch slop value from previous experiment
Change-Id: I7681c401803643f309fd988824602169a830de29
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| e4b8ff8068a96fe467d2334a75198ab762bb915c |
|
07-Dec-2011 |
Adam Powell <adamp@google.com> |
resolved conflicts for merge of 6a828712 to master
Change-Id: I73c804667a890bcc9924951ff655137c1345541a
|
| 7d39f85acf68b3469a2087af488569e356845e22 |
|
06-Dec-2011 |
Adam Powell <adamp@google.com> |
Lower touch slop in ViewConfiguration.
Our typical touchscreens are now good enough that we don't need the
touch slop to be as large as it once was. Lower it to increase
responsiveness while scrolling.
Move the touch slop constant to the config resource
config_viewConfigurationTouchSlop so that it may be more easily
tweaked in device-specific overlays.
Change-Id: I7c11d8affcb98e91654203beb13a26cfeec18f7c
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 006fa48bce7759013d9025376cd5167236c434a7 |
|
28-Oct-2011 |
Gilles Debunne <debunne@google.com> |
Cleaning and new constant in ViewConfiguration
Fixed the documentation and comments for dips versus pixels.
Added a new DOUBLE_TAP_TOUCH_SLOP to replace the hard-coded and
*unscaled* value used in GestureDetector. Assuming this value was
ok for hdpi devices, set it to 20 / 1.5 ~= 16 in dips.
New method kept hidden to keep API unchanged.
Change-Id: I6d237faa2fdb7714e0e3558978af130df9a061a5
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 0c4ccff36930ff4f0292b94ad51e164c9fa060a3 |
|
19-Oct-2011 |
Daniel Sandler <dsandler@android.com> |
Add hasNavigationBar() to the window manager.
It is no longer sufficient to check the value of
internal.R.bool.config_showNavigationBar to determine if a
navigation bar (separate from the status bar) is shown on a
device, because the emulator needs to be able to override
this value (now possible by setting qemu.hw.mainkeys to "1"
or "0", for navbar or no navbar, respectively).
This logic is now contained in PhoneWindowManager, and any
clients wishing to know whether the system has a software
nav bar should consult the new hasNavigationBar() method.
Bug: 5404945
Change-Id: I119d32a8c84b88b2ef46f63244e7f11dc5de0359
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 7f9f99ea11051614a7727dfb9f9578b518e76e3c |
|
11-Aug-2011 |
Xavier Ducrohet <xav@android.com> |
Make some methods/fields package private so that layoutlib can access them.
Change-Id: I4aeadfbaf8a4f6a459fa19937c21ac23d9e5fb64
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 6805545649f2b194859033df94602492b9ec086e |
|
03-Aug-2011 |
Romain Guy <romainguy@google.com> |
Add the ability to enable/disable marquee fading per device
Change-Id: I4211553455e87f0af598a2fac1d4f65f15c294fc
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 8c4706252228755ed181d19532b7e0cfec270ba4 |
|
01-Jul-2011 |
Adam Powell <adamp@google.com> |
Add API to report the presence of a permanent menu key on the device.
Action bar now uses this to determine whether to show an overflow menu.
Change-Id: Ife4f724d02bbc0d9d86d94740c85299f6dacae91
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| a0156177cdc809795dd8bc5a19943dd2b6f82b66 |
|
27-Jun-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Added scroll and text selection change accessibility events.
1. Added scrolling accessibility event to provicde feedback
when a view is scrolled.
Note: We need scroll events for ICS since even though we have
touch exploration the user does not know when something
is scrollable and not feedback is provided while scrolling.
bug:4902097
2. Added a text selection change event to provide feedback
for selection changes including cursor movement.
Note: We need the text selection change events for ICS since
even though the IME supports navigation in text fields
the user receives no feedback for the current selection/
cursor position.
bug:4586186
3. Added a scrollable property to both AccessibilityEvent and
AccessibilityNodeInfo. The info has to describe the source
in terms of all properties that make sense for accessibility
purposes and the event has this property (kinda duplicated)
since clients will aways want to know if the source is
scrollable to provided clue to the user and we want to avoid
pulling the info of the source for every accessibility event.
Change-Id: I232d6825da78e6a12d52125f51320217e6fadb11
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 774ed9d9537c15482e8baca2f2890c5d2f4ffe75 |
|
08-Jun-2011 |
Jeff Brown <jeffbrown@google.com> |
resolved conflicts for merge of 8b2c0014 to master
Change-Id: I33a5a2949dc6c2d09e8196ba8c7128caa7ac2361
|
| 8b2c00144ac262a6fbdbbac1ed8dfe813b883f81 |
|
07-Jun-2011 |
Jeff Brown <jeffbrown@android.com> |
am b3536145: am ed48fa89: Merge "Touch pad improvements. Bug: 4124987" into honeycomb-mr2
* commit 'b3536145725250401d25ffa00cda85d222dfc21e':
Touch pad improvements. Bug: 4124987
|
| bb3fcba0caf697f1d238a2cbefdf1efe06eded99 |
|
07-Jun-2011 |
Jeff Brown <jeffbrown@android.com> |
Touch pad improvements.
Bug: 4124987
Only show one spot per touch point instead of one spot per
finger for multitouch gestures.
Tweaked the pointer acceleration curves.
Dissociated the hover/tap timeouts from the "tap" timeout
since they mean very different things.
Change-Id: I7c2cbd30feeb65ebc12f6c7e33a67dc9a9f59d4c
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| e0a799a2ac1ca78e30fbac9e4e12a063425c08d3 |
|
05-May-2011 |
Patrick Dubroy <dubroy@google.com> |
Only delay pressed feedback for Views inside a scrolling parent
Add a method on ViewGroup to determine whether it supports scrolling.
This allows us to show the pressed feedback immediately in many cases,
improving responsiveness of buttons, etc.
This patch also lengthens the timeout in order to reduce flashes
when the user is scrolling.
Change-Id: Ieb91ae7a1f8e8f7e87448f2a730381a53947996f
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| a3dcd0a3f1b48fc0d675db7e32c27415a14f6d08 |
|
30-Apr-2011 |
Conley Owens <cco3@android.com> |
Merged "Adjust mBiggerTouchSlopSquare to the suitable value"
Conflicts:
core/java/android/view/ViewConfiguration.java
Change-Id: I74de006dbb19fd878591bc90955a1c6e74aa084e
|
| 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/view/ViewConfiguration.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/view/ViewConfiguration.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/view/ViewConfiguration.java
|
| a454767b09ecb7d25d00beae0e5a1fdd48605c63 |
|
03-Mar-2011 |
Jeff Brown <jeffbrown@google.com> |
Get key repeat timeout and delay from ViewConfiguration.
Replaces previously hardcoded values. This ensures that key repeat
takes the accessibility long press timeout setting into account.
Unfortunately the system must be rebooted for the change to take
effect. We will fix that later.
Change-Id: I3ab70bb037331620b7e532170c1727287b5c6f91
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 54d068ec6af0ee6d261a135400efe6816c6f5ffe |
|
02-Mar-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Add system wide management of core settings
bug:3505060
Since we want to have some settings that are used very frequently
by many applications (long-press timeout is one example) these should
be managed efficiently to reduce lookups from different processes
because in the case of a cache miss a disk I/O is performed. Now
the system manages such core settings and propagates them to the
application processes.
Change-Id: Ie793211baf8770f2181ac8ba9d7c2609dfaa32a7
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 0211a0a10d20ec99bd78905ea9cd2960f7beb4c8 |
|
15-Feb-2011 |
Romain Guy <romainguy@google.com> |
Gracefully handle drawing caches allocation failure.
Bug #3431451
This bug was causing ListView to not render properly when showing an item
larger than the maximum drawing cache size. ListView relies on the drawing
cache to correctly mask all the background pixels. However, if the cache
is not properly created, the background will show through even though
ListView.isOpaque() == true. This change detects this case and falls
back to the default non opaque behavior.
Change-Id: I30a45e7a03fb7ebb2b12f0e85c075c2901954c44
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 40209532bff0f83cbbdf408bb3f6e8142e7b02cd |
|
14-Jan-2011 |
Masanori Ogino <ogino.masanori@sharp.co.jp> |
Adjust mBiggerTouchSlopSquare to the suitable value
If the scaling factor is larger than 1.0 (i.e. 1.5),
then mTouchSlopSquare(576) is bigger than mBiggerTouchSlopSquare(400).
The double tap condition should be bigger than a single tap's one.
This causes the fail of the following CTS test cases in the device has
over 240 density.
- android.view.cts.GestureDetectorTest
* testOnTouchEvent
- android.view.cts.GestureDetector_SimpleOnGestureListenerTest
* testSimpleOnGestureListener
To fix this issue, I'll add a new public method
ViewConfiguration#getScaledLargeTouchSlop() then the value returned
from that method is used as a slop area of mLargeTouchSlop.
Change-Id: I0e61c13670e1300be1ccf45a89ef89410496fb48
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 8ce7aab79e711ff5de54985aeffb1a205b7f9942 |
|
25-Jan-2011 |
Gilles Debunne <debunne@google.com> |
Overscoll bounce amplitude is smaller.
Per Dan's request for poor behavior on low speed Overscrolls.
Change-Id: I184133df5e6cc68d8d9bf39edb62d42e13d27a90
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| ff801ec71399f7e8aa95bcbb9937c53144fe17c5 |
|
23-Jan-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #3302006: Cannot see the dialog lunched from a transparent activity.
The activity manager was not performing the layout pass on the new window,
because its app token was still hidden, because the activity manager / window
manager were still waiting for it to be ready to show.
Just ignore whether the app token is hidden for this case.
Also fixes some problems with animations, and tweaks the ViewConfiguration
values for xlarge screens.
Change-Id: Icbe9c77ba8127d1e02df2d6f27b8e86ec842e50a
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 34961cc2e5cd483b15dfd1ff1eb33b01b849e0dc |
|
15-Dec-2010 |
Gilles Debunne <debunne@google.com> |
Reduced Overfling threshold after many different cefficient tries.
Change-Id: Ib655e73fc75a09c6379883871fabf90793a6cff5
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| c35a829b10946fe88b53fd3354b55218ecaff00e |
|
10-Dec-2010 |
Gilles Debunne <debunne@google.com> |
Modified OverScroller curves
When OverFlinged, the scroller goes back to the edge using a spline
instead of a parabolic curve. This ensures that the final velocity of
this movement is null, thus removing the visual discontinuity that can
be observed with the current version.
Bouncing coefficient is deprecated. Changed doc accordingly.
New more expressive spline tension tuning coefficients.
These were tuned to match the one used before the refactoring of CL 81532.
Change-Id: I80dbccebea11544595935077463ad7737c3392e9
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| fff4ab09b6c69e437537f322aaca7829f009ff1d |
|
24-Nov-2010 |
Gilles Debunne <debunne@google.com> |
Refactored OverScroller
Restored the interpolator and a constructor with 4 parameters.
New spline coefficients, spline computation moved to MagneticOverScroller, which has been
renamed SplineOverScroller.
Change-Id: If1ab2653bb998600e9c5d6f46dfd6cd30fa44efc
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 637d337b58d8eec6de19230a5dd5ca5581c0478d |
|
25-Aug-2010 |
Adam Powell <adamp@google.com> |
Merge overscrolling from gingerbread.
Change-Id: I3eb4413261b38ddd8c609d6153bdfd4ae46c6a0f
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 909cbaf8f92d69f507bbdba9e5aa960d1e6c7a1f |
|
14-Oct-2010 |
Romain Guy <romainguy@google.com> |
Don't draw TextView's alpha layers when not needed.
Change-Id: Iedf42cbc62d727f18500c78fcccf2d081a761fec
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| dbc26d2ba13f80a7590c57de2d80530d96832969 |
|
12-Oct-2010 |
Romain Guy <romainguy@google.com> |
Don't draw fully transparent views/primitives.
Change-Id: Icd7d8ef1f57b51a24faf32f7004125e6300d4fdc
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 7627c221c6ce8bf433bf207b002eabe7236c4757 |
|
04-Sep-2010 |
Adam Powell <adamp@google.com> |
DO NOT MERGE Tweak overscroll
Change-Id: I5ba00fc87ba7b286978acf577ba6461f79066437
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 5916882c3f13429d29f95b89dd94bd2d5733da85 |
|
02-Sep-2010 |
Adam Powell <adamp@google.com> |
DO NOT MERGE Overscroll continues; asset and behavior tweaks.
Change-Id: I367643877a397e7b4fa9bd8c40639ff69436e7f0
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 0a77ce277c6ed2aa25bbea5f8cd5687c0720cb68 |
|
25-Aug-2010 |
Adam Powell <adamp@google.com> |
New edge effects for scrolling widgets (overscroll)
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
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| b7ef1d9ec9aa09ecba5a348c939b10f798aff131 |
|
11-Mar-2010 |
Adam Powell <adamp@google.com> |
Make paging touch slop smaller
Change-Id: I36e2623dcc6e3209de51d32841ca68ce322cc5d8
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| de8d0834fc2bc31f011fb3316757883e1b731440 |
|
10-Mar-2010 |
Adam Powell <adamp@google.com> |
Added ViewConfiguration.getScaledPagingTouchSlop()
Change-Id: I9ab5560c4b76d2b87e53d38b10ba8f5ec4868d85
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| e14579bac59aa84523c2bfbfc3f28c7842ec664d |
|
17-Dec-2009 |
Adam Powell <adamp@google.com> |
Tap delays; making tap UI feel better.
Addresses bug 2317577
Views now will not enter PRESSED state until
ViewConfiguration.getTapTimeout() milliseconds have elapsed. This
prevents scrolls and other gestures from causing views to enter
PRESSED state prematurely.
Quick taps within the same view still work as expected. There is now a
PREPRESSED state flag within View to help track quick taps.
If tapped quickly, views will remain pressed for
ViewConfiguration.getPressedStateDuration().
Tap timeout has been changed to 115ms. Pressed state duration has been
changed to 125ms.
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| f116bf8884b5b58aae261d148003811aa4a7c6e9 |
|
28-Sep-2009 |
Mike Cleron <mcleron@google.com> |
Fading scrollbars return. But you have to opt in.
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 3e2ac8843489e83c4171aabcfe98769b5159a5c8 |
|
25-Sep-2009 |
Dianne Hackborn <hackbod@google.com> |
Fix/improve issue #2142662: too easy to click a link/item instead of fling
Reduce the slop.
Change-Id: If255e68cc8092e7f746a91c0fea27abfc5292b73
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 4296fc4d326447875c26a925f12b3935632f13bb |
|
06-Jul-2009 |
Romain Guy <romainguy@android.com> |
Fixes #1444844. Set a maximum fling velocity in scrollable views.
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| f8a7ceaef2e7d5cd530c9426bde91b6fa9a40b75 |
|
11-Apr-2009 |
Andy Stadler <> |
AI 145778: Manual merge changes 145382-145384 from cupcake.
Automated import of CL 145778
/frameworks/base/core/java/android/view/ViewConfiguration.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/view/ViewConfiguration.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/view/ViewConfiguration.java
|
| 076357b8567458d4b6dfdcf839ef751634cd2bfb |
|
03-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@132589
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 3dec7d563a2f3e1eb967ce2054a00b6620e3558c |
|
03-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@137055
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 3001a035439d8134a7d70d796376d1dfbff3cdcd |
|
19-Feb-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake/...@132276
/frameworks/base/core/java/android/view/ViewConfiguration.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/view/ViewConfiguration.java
|
| f013e1afd1e68af5e3b868c26a653bbfb39538f8 |
|
18-Dec-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Code drop from //branches/cupcake/...@124589
/frameworks/base/core/java/android/view/ViewConfiguration.java
|
| 54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/view/ViewConfiguration.java
|