| f93bb6d8fd81d8938b16cf40259f97c336e9ef3a |
|
13-Dec-2011 |
Adam Powell <adamp@google.com> |
Bug 5727679 - CTS test ViewGroupTest#testGetChildVisibleRect
Preserve the ability to call getChildVisibleRect without the view
being attached to a window.
Change-Id: I702b19fa1625c346eb22fda4a4ffb6e8f790b689
/frameworks/base/core/java/android/view/ViewGroup.java
|
| c7ee3cab56b8cc90c4f6659a262a1cba5c71e92a |
|
08-Dec-2011 |
Romain Guy <romainguy@google.com> |
Remove dangerous and useless optimization
Bug #5525888
Change-Id: I553828c0da09b15d0dce3727e4c26a9d0bcf72ea
/frameworks/base/core/java/android/view/ViewGroup.java
|
| cea45132e3d5d32a6fc737abf10b8893a50f465b |
|
24-Nov-2011 |
Gilles Debunne <debunne@google.com> |
Handle animations in Views' rectangle clipping methods.
getChildVisibleRect and getLocationInWindow do not take the new
mTransformationInfo View attribute.
As a result, these methods return invalid value during an animation
Bug 5638710
Changes in Patch Set 2:
- temporary allocations removed using static thread local variables (method
calls are NOT reentrant).
- scroll should be handled *before* applying the transformation matrix.
Fixed the call order in View#getLocationInWindow()
Patch set 4: fix from comments.
Patch set 5: <p>s
Change-Id: I15dc44c0659305d9029c59a47aba3a738bb35ae1
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 7077506f9945b87b02bdd47ffce75a5b813c821c |
|
14-Nov-2011 |
Dave Burke <daveburke@google.com> |
Revert "Discard framebuffer rendering queues when discarding layers"
This reverts commit da96f8ac2c1c35a54f3f36e6d776cb386a251d03.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| da96f8ac2c1c35a54f3f36e6d776cb386a251d03 |
|
11-Nov-2011 |
Romain Guy <romainguy@google.com> |
Discard framebuffer rendering queues when discarding layers
Bug #5581817
Change-Id: If612846ec5f7793710fc4df152791fb32c506551
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 6e42470f928bbf60c9fd3d17a2a69a4b96cec170 |
|
02-Nov-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Merge "Accessibility window query APIs should respect root name space." into ics-mr1
|
| 0500b3cfda5192efc09d6d4344b0c6c785c0a815 |
|
01-Nov-2011 |
Dianne Hackborn <hackbod@google.com> |
Some optimizations.
- Don't try to create a thumbnail bitmap on the client side. This
wastes 64k, and isn't needed since we are doing screenshots.
- Optimize View to put all of the callback pointers out of line.
Added a couple new APIs so these don't need to be protected/public.
- Lazily create ViewGroup's cache paint.
- Change FrameworkPerf app to not use HW accel drawing, to give better
comparison with GB.
Change-Id: Iec56d02459820d74a4cc9c7ec9c1856563c82c7b
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 57f3b566db630233087b121d3d43ecd81a6dfd95 |
|
01-Nov-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Accessibility window query APIs should respect root name space.
1. The window query API used to not-respect the root name space
while traversing the parent relation i.e. a client was able
to fetch the parent of a root name space node.
2. Children that are root name space were reported but their descendants
not. Actually such children should not be reported since they are
the root of a separate logical sub-tree. Such a tree is exposed by
its root allowing its traversal. The accessibility APIs should be
able to explore a virtual tree, i.e. one with a descendant which is
root name space, only if an accessibility event from there was received.
bug:5480096
Change-Id: I4c4d805aa2f6d4edba86eda213b5239bea83eed2
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 558459fe85f56f29a6ed6a4d0adb4a0bd6665884 |
|
14-Oct-2011 |
Joe Fernandez <joefernandez@google.com> |
docs: add developer guide cross-references, Project ACRE, Round 2
Change-Id: I39a534ae3a2a34b4dabc333a09961012ef911d3e
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 9a230e01a1237749a8a19a5de8d46531b0c8ca6a |
|
06-Oct-2011 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #5371530: SYSTEMUI_FLAG_HIDE_NAVIGATION reasserts itself immediately
This cleans up how ui flags are managed between the client and window manager.
It still reports the global UI mode state to the callback, but we now only clear
certain flags when the system goes out of a state (currently this just means the
hide nav bar mode), and don't corrupt other flags in the application when the
global state changes.
Also introduces a sequence number between the app and window manager, to avoid
using bad old data coming from the app during these transitions.
Change-Id: I40bbd12d9b7b69fc0ff1c7dc0cb58a933d4dfb23
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 2cdedffcfa5594f9d516fa235d5edf4d4f92c21d |
|
03-Oct-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Accessibility services cannot obtain the source of an event coming from a root namespace descendant.
1. The user can touch the screen at an arbitrary location potentially crossing the root namespace
bounday which will send an accessibility event to accessibility services and they should be able
to obtain the event source. Also accessibility ids are guaranteed to be unique in the window.
Added a package scoped findViewByAccessibilityId method that dives into nested root namespaces.
2. Added accessibility support to the AnalogClock.
bug:5405934
Change-Id: I84edcb554bae41aafcbbc2723c5e62c1ef8a6ddf
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 59c7f80dd20258cefa1fc4bdd3c9a709a8dd53b8 |
|
30-Sep-2011 |
Romain Guy <romainguy@google.com> |
TextureView works best when it draws stuff.
Bug #5391188
Change-Id: I5e754881ccb08ff288ebd60de77282c9cbcf3f86
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 2fcbbd0363633765e1ab5b9890ccb807002370e8 |
|
29-Sep-2011 |
Adam Powell <adamp@google.com> |
Fully qualify javadoc links and make the tools happy
Change-Id: I2ad839be71b550a2bcfb90f67627afdd10d3ae14
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 2a9fa89643ce796ee6dc7edae2742b291b6c5f40 |
|
29-Sep-2011 |
Romain Guy <romainguy@google.com> |
Don't build display lists for views with a layer.
This could cause the draw() code of views to be invoked too often
or worse, called with the wrong canvas. For instance, a view backed
by a software layer could get its draw() method called to record a
display list. Using a software layer is the recommended way to use
drawing operations not supported in hardware. Since we would
sometimes call the draw() method with the hardware backend anyway,
the app could crash by executing an unsupported operation.
Change-Id: Ib5f9a3a4c6f3efff5e0162ecd73d2dffe06e30a6
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 6e6db61809a9cf31f110fb53be09b43cfb9f14de |
|
26-Sep-2011 |
Chet Haase <chet@google.com> |
Fix display list issue that was crashing an external app.
The app was removing a View whilst in its onDraw() method. This meant
that we asked it for its display list and it invalidated that display list
(by removing itself) before it returned from onDraw(). We later attempted to
draw that invalid display list into its parent nad died in native code.
The fix is to check the state of the display list after the call to getDisplayList()
and to avoid doing further work with it if it's invalid.
Change-Id: I14a342b4fe79c8dce2626ff61237b447040e7f42
/frameworks/base/core/java/android/view/ViewGroup.java
|
| b84b94e1a04cd1f396dd6fef98d65ca1a2729c92 |
|
23-Sep-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Scroll accessibility events should not populate text.
Scroll events are used to report position change and should not
contain the text content of the view that fires them because it
is usiually a containter for many other views and the text will
be long and not informative for accessibility purposes. Also
such evens are fired relatively frequently. If a client wants
to fetch some textual content for a scroll event he can use
the interrogation APIs.
bug:5352059
Change-Id: I43e02aca895c8ab16ba82ebe1cee3aea8ce7711a
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 4b86788003b3ddc968d0681d5ed4e5da07e4a65a |
|
16-Sep-2011 |
Adam Powell <adamp@google.com> |
Bug 5244365 - Prevent views from receiving multiple onAttachedToWindow
calls.
If a View is added to a ViewGroup during the ViewGroup's
onAttachedToWindow method, the child can receive two calls to
onAttachedToWindow. Guard against this.
Change-Id: I845d0cb2c9172071eee1eadc6bc2dd282ee0ef43
/frameworks/base/core/java/android/view/ViewGroup.java
|
| ea515aeafa01de6f50c854ee381b972ef2478284 |
|
15-Sep-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Update the public APIs for finding views by text to optionally use content description.
1. Added flags to the search method to specify whether to match text or
content description or both.
2. Added test case for the seach by content description.
3. Updated the code in AccessibilityManager service to reflect the latest
changes there so test automation service works - this is the fake
service used for UI automation.
Change-Id: I14a6779a920ff0430e78947ea5aaf876c2e66076
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 031d9c1389de2b9dac7f175af0b962e24b21d5be |
|
10-Sep-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding accessibility delegate mechanism for backwards compatibility support.
1. Added an AccessibilityDelegate class in View which can be set by
a client that wants to cutomize accessibility behavior via
composition as opposed to inheritance. Insead overriding a new method in
View thus being bound to the API version that introduced this
method a developer can conditionally inject the accessibility
customization if the platform API version is heigh enough. The
developer will have to override the method of interest of the
delegate. The default implementation of the delegate methods is
the same as that of View in the case that there is no delegate
set. If a delegate is set calling an accessibility related method
on View will be handed off to the corresponsing method of the
delegate.
bug:5259555
Change-Id: I00e750e22e5e7164a1b571cb3d12ecaf4ab93db4
/frameworks/base/core/java/android/view/ViewGroup.java
|
| aceafe63eeb7d3bfc05ef5ab0b3957572d61ecf5 |
|
27-Aug-2011 |
Chet Haase <chet@google.com> |
Fixed error in invalidation/LayoutTransition logic
A recent fix for invalidation noop'd calls to invalidate() on
GONE/INVISIBLE views. This logic also noop'd views which might
be GONE, but which are in the process of fading in/out via
LayoutTransition animations. These views should invalidate as
usual.
Change-Id: Ie90a340f70290391a3aa4e68df535c6aabf4e5eb
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 530b22ab4e9076926e13502b443e3ce3879b45ae |
|
23-Aug-2011 |
Chet Haase <chet@google.com> |
Fix invalidation roundoff error with old animations
We need to add .5 to the width/height of invalidation areas to
avoid truncation errors.
Change-Id: Iaa2407a91a6a7f6d729af21d45e77e436197df11
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 1abf7fa1d1930e24739cae9874970420101bc2f9 |
|
18-Aug-2011 |
Chet Haase <chet@google.com> |
Fix potential null deref in ViewGroup when running transition
Change-Id: I9075c4a05e19122592145468e220afa43faee540
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 4dfbec2665bd5f567d7321f2e88a39e1ab45fdf8 |
|
15-Aug-2011 |
Jeff Brown <jeffbrown@google.com> |
Find next focus id from inside-out.
Bug: 5165543
This change fixes some problems when the view hierarchy contains
duplicate ids, such as when ListViews contain nested custom views.
If the custom views contain next focused id hints, then the system
should prefer the other views within the ListView item over any
other views outside of the ListView item.
Change-Id: I5653ff6bac0bf9f08bd6ecbe5a3bb22ea47ab566
/frameworks/base/core/java/android/view/ViewGroup.java
|
| ea83503e8683531fac2534047e50bc1e5979b6dd |
|
29-Jul-2011 |
Romain Guy <romainguy@google.com> |
Don't create hw layers when there's no hw context.
Bug #5093805
Change-Id: Ia58b3381c83b9a200e80020e5c1b9c337ad6c35c
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 93b2182a2e1a42ef60d3c0fa79fbdc4b27875685 |
|
28-Jul-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
AccessibilityNodeInfo reports no children for the topmost view in the tree.
1. My previous change to restrain AccessibilityNodeInfo to report children
if it is root namespace did not take into account that the tompost view
i.e. the decor view actually is a root namespace. Adding check to allow
the info to report children of rthe topmost view but do not do so if a
descendant is flagged as root namespace.
bug:5086988
Change-Id: Ib82b8ebe5a2c287ab1c5333d130ec50eb9ced78c
/frameworks/base/core/java/android/view/ViewGroup.java
|
| effe10fd67645bcaeb987dfefa154c284771064e |
|
27-Jul-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
findViewWithText inconsistent with other findView* methods and AccessibilityNodeInfo not respecting root namespace.
1. Find viewsWithText does not respect if the current view group is a root name
space and keeps its traversal. This is inconsistent with the other findView*
methods. Also only visible views are returned witch is inconsistent with the other
findView* methods.
2. AccessibilityNodeInfo reports children it the source is root namespace. This is
not correct since thi flag denotes the beginning of a logically separate view
hierarchy.
bug:5082601
Change-Id: I9c7ca51f284d04728828d5e656112257c9a2c6e2
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 29d23ecfd8612ecd4a7b2140acd344934b73a558 |
|
25-Jul-2011 |
Romain Guy <romainguy@google.com> |
Add debug flag to print out the EGL configuration used by libhwui
Change-Id: I8be5aebb60b7441342d430131168d11dc551ec34
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 5bae58dff90025dd1419bd7508d17bbd32c26beb |
|
23-Jul-2011 |
Romain Guy <romainguy@google.com> |
Merge "Nested alpha animations should cause invalidates too Bug #5041061"
|
| d4745a689f36211afaff396874d78b1d5202762d |
|
23-Jul-2011 |
Romain Guy <romainguy@google.com> |
Nested alpha animations should cause invalidates too
Bug #5041061
Change-Id: I96835449b6b5537872afda90956c5d06d826e841
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 6179ea3196e9306d3f14361fe9ef14191b1edba6 |
|
28-Jun-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding accessibility support to the Status Bar.
1. Added content description to pretty much all animals
in the zoo including buttons in the navigation bar,
notifications and status icons for battery, signal,
data, etc.
2. Rectored to avoid ovelaying views since they block
touch exploratino. In general overlaying views
cause trouble for touch exploration and accessibility
in general.
3. Avoid sending accessibility events in case the user is
touching outside of the StatauBAr panels to avoid
confusion.
4. Added records to accessibility events in the places where
this would help the presentation. So the event comes from
a given "leaf" view and its predecessor is adding a record
to the event for itself to provide more cotext. It is up
to the accessiiblity service to choose how to present that.
bug:4686943
Change-Id: I1c1bd123d828fb10911bca92130e9a05c1f020b3
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 350f0a63c9e785304063a95a6df9e128a67ec64f |
|
19-Jul-2011 |
Philip Milne <pmilne@google.com> |
Expose to the platform the ability to pick up changes in child visibility.
Also:
. use above, to flsuh GridLayout state when child's GONE state changes.
Change-Id: I8567c24b51b807f0625918d42b6847a5a350311d
/frameworks/base/core/java/android/view/ViewGroup.java
|
| db94b0a5b071bafd5ae8cb9735528aa9d4b31cc8 |
|
19-Jul-2011 |
Chet Haase <chet@google.com> |
Merge "Don't constrain invalidation rect when not clipping children"
|
| a3db866056adb01820bbd6389d20fc550be87eb3 |
|
19-Jul-2011 |
Chet Haase <chet@google.com> |
Don't constrain invalidation rect when not clipping children
View.setClipChidlren(false) allows children to draw outside of their containers.
But logic in ViewGroup.invalidateChildInParent() constrains the invalidation
rectangle to the bounds of the parent, making the flag useless in some situations.
Avoid intersecting the dirty rect with the parent bounds when the parent
is set to not clip its children.
Change-Id: Icc485b539758c96da0bd62ef57974a1bcb94f866
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 2e29de7cab35e4cf7c8f177b546cc95b101ed5c8 |
|
19-Jul-2011 |
Philip Milne <pmilne@google.com> |
Merge "Gather View's hierarchy notifications into methods that can easily be overidden."
|
| f51d91c3ab232154b6c00d7f71377ff2421f79bf |
|
19-Jul-2011 |
Philip Milne <pmilne@google.com> |
Gather View's hierarchy notifications into methods that can easily be overidden.
Also:
. Remove backward compatibility Group class now that AppsCustomizePagedView has been updated.
Change-Id: Ie3eabbdf57a539b28cdc3fd6d48cd984a4014960
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 6dd005b48138708762bfade0081d031a2a4a3822 |
|
18-Jul-2011 |
Dianne Hackborn <hackbod@google.com> |
I. Can. Not. Stand. ViewAncestor.
It was done so we would have the name "ViewRoot" available for a
public API. However, the name "ViewAncestor" just makes no sense.
So instead, change it to ViewRootImpl.
Change-Id: If9599ca67896f339f6fefa7d1dde121201171d97
/frameworks/base/core/java/android/view/ViewGroup.java
|
| cb379120456d8065d742021fc5c66748fc8a11a8 |
|
07-Jul-2011 |
Doug Felt <dougfelt@google.com> |
Implement textDirection heuristic selection.
Change-Id: I2fcf18de573f2d66494fa5ed61e4273c3c6078c7
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 7f86c806ada21fc7a3feefd89d6fcb4282b0af40 |
|
02-Jul-2011 |
Fabrice Di Meglio <fdimeglio@google.com> |
Fix View reset of layoutDirection and textDirection
- do it in onDetachedFromWindow()
- make naming consistent too
- update unit tests
Change-Id: I320fcdbf75166bae793c4409e7344608b696667f
/frameworks/base/core/java/android/view/ViewGroup.java
|
| b2479153b743df9e54f7e17c7132a5ecd87fa453 |
|
08-Jul-2011 |
Romain Guy <romainguy@google.com> |
Correctly position layers.
Change-Id: I1678b1c5bdab140b44e56556c50ab8329255f18a
/frameworks/base/core/java/android/view/ViewGroup.java
|
| f03712bf540db15d0594b848e63c207fd50e9379 |
|
02-Jul-2011 |
Fabrice Di Meglio <fdimeglio@google.com> |
Merge "Fix default TextView textDirection heuristic"
|
| 0b28c757adfec4302b144d8230c01c04ae00ca2b |
|
01-Jul-2011 |
Fabrice Di Meglio <fdimeglio@google.com> |
Fix default TextView textDirection heuristic
- use "first strong" instead of "locale"
- optimize "any rtl" heuristic too
- fix a few wording issues too
Change-Id: I239a11a49a7a6a6d45165f593c96e8b6b84f0661
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 0e591ab277e777b0422463823e3abf28bb1fd5d8 |
|
01-Jul-2011 |
Fabrice Di Meglio <fdimeglio@google.com> |
Merge "Add charCount heuristic to TextView textDirection"
|
| 8f5026562f26dcde43ee9d9182b309c3204dc1ad |
|
30-Jun-2011 |
Fabrice Di Meglio <fdimeglio@google.com> |
Add charCount heuristic to TextView textDirection
- threshold set to 60% (using a constant)
- fix also one issue during layout direction resolution (parent could be null so delay resolution
up to when parent is no more null)
Change-Id: I65f24a297aac6bc0d5d482ee31b55db0b201e5bf
/frameworks/base/core/java/android/view/ViewGroup.java
|
| fe8b06cfb4cb4991bcfd09ffa60dcbb7b48ee45f |
|
30-Jun-2011 |
Fabrice Di Meglio <fdimeglio@google.com> |
Merge "Support control of text alignment."
|
| 8ef7358fb3039765b98df170fea4307935145305 |
|
30-Jun-2011 |
Jeff Brown <jeffbrown@google.com> |
Merge "Synthetic cancel event should have touchscreen source."
|
| 2fdbc5a0c499752285630336f0ef538d4a50e60e |
|
30-Jun-2011 |
Jeff Brown <jeffbrown@google.com> |
Synthetic cancel event should have touchscreen source.
Fixed a warning identified by the InputEventConsistencyVerifier
due to some code that synthesizes a touch event which it sends
to onTouchEvent with no input device source specified.
This is generally harmless but a fake source is better than
none in this case.
Change-Id: I44cfa36a4746f598f8fde3086084af3896e2ba2a
/frameworks/base/core/java/android/view/ViewGroup.java
|
| c0ccf0c47c00942a9d0f2670600a8f2d4d7adb5b |
|
24-Jun-2011 |
Doug Felt <dougfelt@google.com> |
Support control of text alignment.
Change-Id: Id6f3682f67ba2e6811e3014cd34a281e6dd0a469
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 222688682e6e072076489d8203d01bdf2366101a |
|
28-Jun-2011 |
Fabrice Di Meglio <fdimeglio@google.com> |
Add textDirection support for TextView and ViewGroup
- use ViewGroup inheritance if defined
- use different heuristics (inherit, firstStrong, anyRtl, ltr, rtl)
- add more unit tests
Change-Id: Ic1325aa7d9e4689b181e0a2d08b7dd7fb3f0dbeb
/frameworks/base/core/java/android/view/ViewGroup.java
|
| b76023afd192a1f5c81a8965cfd1b9dde2558726 |
|
21-Jun-2011 |
Fabrice Di Meglio <fdimeglio@google.com> |
Introduce MarginLayoutParams marginStart and margingEnd
- update BiDiTest app for adding more unit tests concerning margin
Change-Id: Ia6a7e0a1948a2c375e8f3cc87d120a85351a8c27
/frameworks/base/core/java/android/view/ViewGroup.java
|
| a54a600bc41c8ac760f85333b0c562cdc6770531 |
|
24-Jun-2011 |
Fabrice Di Meglio <fdimeglio@google.com> |
Merge "Fix bug #4813026 resolved direction of view doesn't change after layout direction changes"
|
| a9489274d67b540804aafb587a226f7c2ae4464d |
|
23-Jun-2011 |
Romain Guy <romainguy@google.com> |
Add the ability to specify the opacity of a TextureView
TextureView assumes its content is opaque by default.
Change-Id: Iba873423566a5b67c388081838bd910dceba32ba
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 80dc53d652b060d4dea7d70e9a5aa3b8321bcf8d |
|
22-Jun-2011 |
Fabrice Di Meglio <fdimeglio@google.com> |
Fix bug #4813026 resolved direction of view doesn't change after layout direction changes
- reset resolution if setLayoutDirection() is called
- propagate resolution reset to the children if the View is a ViewGroup and direction is inherited
Change-Id: Iab1a75b17426aead7e28caba827614d7cf8e9450
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 87b7f805b94f5df53343264509f6d606d96dfb05 |
|
22-Jun-2011 |
Jeff Brown <jeffbrown@google.com> |
Send hover to all children under pointer.
Previously we only sent hover to the topmost child, but this doesn't
handle cases where multiple children are overlapped to achieve
certain special effects. Now we send hover to all children until
one of them handles it.
Also moved the call to send the accessibility event into the
main dispatch function so that we can send the accessibility event
for all innermost hovered views even when setHovered() might
not be called.
Change-Id: I6fb8b974db44b594c441deafc012b8415afdfac7
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 10b6290c5f15ae512a2f6b5bf8d95bd2527c7235 |
|
21-Jun-2011 |
Jeff Brown <jeffbrown@google.com> |
Only handle onHoverEvent in actionable views.
Modified onHoverEvent so that a view only has its state changed to
hovered when the view is clickable. The intent is to prevent labels
from taking hover focus away from their containing view group despite
not being actionable in any way. The child will still receive
a hover event but, if it does not handle the event (returns false),
the hover event will bubble up to its parent and ancestors allowing
them a chance to handle the event instead.
The new onHoverEvent semantics are better because now they closely
mirror those of onTouchEvent. This makes it straightforward to
implement views that respond to hover by changing their visual
appearance (such as by making buttons glow when hovered).
Added onInterceptHoverEvent to enable ViewGroups to explicitly
intercept hover events within their bounds.
Exposed the new hover event API for real.
Change-Id: I63195c8f5c74b859f6047487f9a0f703e8f40ffe
/frameworks/base/core/java/android/view/ViewGroup.java
|
| ea1da3d2e61625afcc7753ba2e03c5d2fb565dae |
|
16-Jun-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Invisible views should not be visible to accessibility services (interrogation)
1. Infisible children of a ViewGroup are reported by View group
while constructing an AccessibilityNodeInfo.
2. AncestorView does not check whether a found view is shown before
returining it or perform action on it.
bug:4672230
Change-Id: Ic620ea71b7755c598407bdd813a2beeee400c89c
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 8643aa0179e598e78d938c59035389054535a229 |
|
20-Apr-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Interrogation of the view hierarchy from an AccessibilityService.
1. Views are represented as AccessibilityNodeInfos to AccessibilityServices.
2. An accessibility service receives AccessibilityEvents and can ask
for its source and gets an AccessibilityNodeInfo which can be used
to get its parent and children infos and so on.
3. AccessibilityNodeInfo contains some attributes and actions that
can be performed on the source.
4. AccessibilityService can request the system to preform an action
on the source of an AccessibilityNodeInfo.
5. ViewAncestor provides an interaction connection to the
AccessibiltyManagerService and an accessibility service uses
its connection to the latter to interact with screen content.
6. AccessibilityService can interact ONLY with the focused window
and all calls are routed through the AccessibilityManagerService
which imposes security.
7. Hidden APIs on AccessibilityService can find AccessibilityNodeInfos
based on some criteria. These API go through the AccessibilityManagerServcie
for security check.
8. Some actions are hidden and are exposes only to eng builds for UI testing.
Change-Id: Ie34fa4219f350eb3f4f6f9f45b24f709bd98783c
/frameworks/base/core/java/android/view/ViewGroup.java
|
| cca2c9807206f320bd41bf8656a227e4f249e4ba |
|
20-May-2011 |
Chet Haase <chet@google.com> |
Add ability to transition parent hierarchy in layout transitions
This change compensates for changes in the parent hierarchy of
transitioning views. It automatically animates parents with the same
animations as those used for the CHANGING animations run on the container
children.
Change-Id: I86471d16a9070b024cc09c8f6e0f504a881fa99f
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 02739a8eecce26783350041da332f8daf6691e25 |
|
16-May-2011 |
Romain Guy <romainguy@google.com> |
Fix javadoc issues
Change-Id: Ife66a8664955ac1a79b6ffd0080000c820f24632
/frameworks/base/core/java/android/view/ViewGroup.java
|
| fe9f8ab03a63b1037f07dd85799fbea80ec6adaa |
|
07-May-2011 |
Jeff Brown <jeffbrown@google.com> |
Add initial API for stylus and mouse buttons.
Added the concept of pointer properties in a MotionEvent.
This is currently used to track the pointer tool type to enable
applications to distinguish finger touches from a stylus.
Button states are also reported to application as part of touch events.
There are no new actions for detecting changes in button states.
The application should instead query the button state from the
MotionEvent and take appropriate action as needed.
A good time to check the button state is on ACTION_DOWN.
As a side-effect, applications that do not support multiple buttons
will treat primary, secondary and tertiary buttons identically
for all touch events.
The back button on the mouse is mapped to KEYCODE_BACK
and the forward button is mapped to KEYCODE_FORWARD.
Added basic plumbing for the secondary mouse button to invoke
the context menu, particularly in lists.
Added clamp and split methods on MotionEvent to take care of
common filtering operations so we don't have them scattered
in multiple places across the framework.
Bug: 4260011
Change-Id: Ie992b4d4e00c8f2e76b961da0a902145b27f6d83
/frameworks/base/core/java/android/view/ViewGroup.java
|
| b51cc1dd63808da505cd8beb7300f57dc98ff1d3 |
|
05-May-2011 |
Patrick Dubroy <dubroy@google.com> |
Merge "Only delay pressed feedback for Views inside a scrolling parent"
|
| 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/ViewGroup.java
|
| c6cc0f8c19d9eccf408a443fa2bf668af261dcd0 |
|
12-Apr-2011 |
Joe Onorato <joeo@google.com> |
Rename ViewRoot to ViewAncestor.
ViewRoot is about to be a new public class for poking at ViewAncestor.
Change-Id: Ie95d707c6d8bbb48f78d093d7b2667851812a7d5
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 9fc27819d75e24ad63d7b383d80f5cb66a577a0d |
|
27-Apr-2011 |
Romain Guy <romainguy@google.com> |
Correctly compute tex coords for rect layers.
Bug #4192695
This change also fixes Javadoc links in the framework.
Change-Id: Ia548bcb18baba5d6fe6a4a04a2278e3a3bd465b2
/frameworks/base/core/java/android/view/ViewGroup.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/view/ViewGroup.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/ViewGroup.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/ViewGroup.java
|
| bbdc50b102faf52768ac3028bc49e027ff140656 |
|
20-Apr-2011 |
Jeff Brown <jeffbrown@google.com> |
Track unhandled input events in consistency verifiers.
This fixes spurious verification errors that would be generated
when a view declined an initial event such as ACTION_DOWN. Since
the view would not receive the rest of the event stream, it would
not see the corresponding ACTION_UP and the next ACTION_DOWN would
trigger a spurious verification error.
Change-Id: I2386acf378cd1765d5446faed5ad9c6525f8b400
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 21bc5c917d4ee2a9b2b8173091e6bba85eaff899 |
|
01-Mar-2011 |
Jeff Brown <jeffbrown@google.com> |
Add a little input event consistency verifier.
The idea is to assist with debugging by identifying cases in which
the input event stream is corrupted.
Change-Id: I0a00e52bbe2716be1b3dfc7c02a754492d8e7f1f
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 3d4bf17f49b82355b3b82d8bdaec4d65c4293bc9 |
|
29-Mar-2011 |
Christopher Tate <ctate@google.com> |
Add view/drawable states for drag-accepting / drag-hovered
Added new drag_can_accept and drag_hovered XML attributes and the View
logic to support them. Drawable states are now refreshed automatically
when a drag starts/ends and when a drag crosses the boundary of a
participating view.
Change-Id: I25f8ee02c83b3fa4f27201997d7eabf4be653fd8
/frameworks/base/core/java/android/view/ViewGroup.java
|
| b7c25ce3aef3c6e930fc3f31436f52aed8ebed14 |
|
24-Mar-2011 |
Jeff Brown <jeffbrown@google.com> |
Merge "Add MotionEvent.HOVER_ENTER and HOVER_EXIT."
|
| a032cc008618b83ecbbede537517d1e7998e3264 |
|
08-Mar-2011 |
Jeff Brown <jeffbrown@google.com> |
Add MotionEvent.HOVER_ENTER and HOVER_EXIT.
The input dispatcher sends a HOVER_ENTER to a window before dispatching
it any HOVER_MOVE events. For compatibility reasons, the window will
*also* receive the HOVER_MOVE. When the pointer moves into a different
window or the pointer goes down or when events are canceled for some reason,
the input dispatcher sends a HOVER_EXIT to the previously hovered window.
The view hierarchy behavior is similar. All views under the pointer
receive onHoverEvent with HOVER_ENTER followed by any number of HOVER_MOVE
events. When the pointer leaves a view, the view receives HOVER_EXIT.
Similarly, if a parent view decides to capture hover by returning true
from onHoverEvent, the hovered descendants will receive HOVER_EXIT.
The default behavior of onHoverEvent is to update the view's hovered
state by calling setHovered(true/false). Views can query their current
hovered state using isHovered().
For testing purposes, the hovered state is mapped to the pressed
drawable state. This will change in a subsequent commit with the
introduction of a new hovered drawable state.
Change-Id: Ib76a7a90236c8f2c7336e55773acade6346cacbe
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 13f35f3ce6a7d26c20d1c63485bfb5e2ffff31b9 |
|
24-Mar-2011 |
Romain Guy <romainguy@google.com> |
Correctly check bottom padding in setPadding().
Change-Id: Ie8099d37ad865acc559c4a4d34eb84960a1a19f3
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 7b5b6abf852c039983eded25ebe43a70fef5a4ab |
|
15-Mar-2011 |
Romain Guy <romainguy@google.com> |
Fix rendering artifact in edge fades.
Bug #4092053
The problem always existed but was made visible by partial invalidation.
When saving a layer, the renderer would try to postpone glClear()
operations until the next drawing command. This however does not work
since the clip might have changed. The fix is rather simple and
simply gets rid of this "optimization" (that turned out to be
usless anyway given how View issues saveLayer() calls.)
This change also fixes an issue with gradients (color stops where
not properly computed when using a null stops array) and optimizes
display lists rendering (quickly rejects larger portions of the
tree to avoid executing unnecessary code.)
Change-Id: I0f5b5f6e1220d41a09cc2fa84c212b0b4afd9c46
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 2243e555b061254f7f0f72ca1d6cd44db6c266fa |
|
08-Mar-2011 |
Romain Guy <romainguy@google.com> |
Correctly handle opaque fading views
Bug #3475554
Change-Id: Ia4915ada67046486103dfc6f08e4dac8564f85dd
/frameworks/base/core/java/android/view/ViewGroup.java
|
| bc8a8e8c926115cb7b3910d016e5cff12b0f7b0a |
|
08-Mar-2011 |
Romain Guy <romainguy@google.com> |
Merge "Add support for partial invalidates in WebView Bug #3461349" into honeycomb-mr1
|
| cabfcc1364eb7e4de0b15b3574fba45027b45cfc |
|
08-Mar-2011 |
Romain Guy <romainguy@google.com> |
Add support for partial invalidates in WebView
Bug #3461349
This change also fixes two bugs that prevented partial invalidates
from working with other views. Both bugs were in our EGL implementation:
they were preventing the caller from comparing the current context/surface
with another context/surface. This was causing HardwareRenderer to always
redraw the entire screen.
Change-Id: I33e096b304d4a0b7e6c8f92930f71d2ece9bebf5
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 3ba8f5d675831647e45d0ce11507c85dfb5f753b |
|
08-Mar-2011 |
Adam Powell <adamp@google.com> |
Fix bug 4021346 - crash while navigating
Change-Id: Iff60c5f4214c56597f2a1b393982d023866e490e
/frameworks/base/core/java/android/view/ViewGroup.java
|
| e8e45d32fd1f67fed1b70d0fc19d2f91a76f128e |
|
03-Mar-2011 |
Chet Haase <chet@google.com> |
Cancel LayoutTransition animations selectively
A recent change to LayoutTransition caused new layout transitions to
cancel any previously-running animations. This was to handle situations
where a transition adding an item needed transitions removing items to
finish their job first (and vice versa). But canceling *all* running
animations from transitions caused some artifacts, like making the status
bar icons blink or fade in, depending on which one was started last.
The new approach is to cancel just the ones we care about: adding animations
cancel removing animations, and vice versa. Either one cancels 'changing'
animations, which prevents objects from being animated to the old end
locations, since the new transition will animate them to the correct new
end locations.
Change-Id: I68ac351b05365cace6639b6618422395c35c83fd
/frameworks/base/core/java/android/view/ViewGroup.java
|
| a7dabcd3dfb263468613fa2b04909c8fabb66a9d |
|
02-Mar-2011 |
Romain Guy <romainguy@google.com> |
Don't account for scrollX/Y when drawing a display list in a layer.
Change-Id: I73bdcdab3e547d00ba2853aed550e65d5f8c6fcd
/frameworks/base/core/java/android/view/ViewGroup.java
|
| d643bb56fdf21973ea75984f0816b7dc024698df |
|
01-Mar-2011 |
Romain Guy <romainguy@google.com> |
Correctly mark layers dirty when drawing WebView.
Change-Id: I7ae0c3cfa0916d8fbeaf01e8da127c621a06a0f4
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 33bbfd2232ea9eaae9a9d87a05a95a430f09bd83 |
|
25-Feb-2011 |
Jeff Brown <jeffbrown@google.com> |
Add support for mouse hover and scroll wheel.
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
/frameworks/base/core/java/android/view/ViewGroup.java
|
| cc0c159e9b3dd4e0f48da0ce3e33d2c68a651413 |
|
19-Feb-2011 |
Jeff Brown <jeffbrown@google.com> |
Add new hover move action and scroll wheel plumbing.
Added support for tracking the mouse position even when the mouse button
is not pressed. To avoid confusing existing applications, mouse movements
are reported using the new ACTION_HOVER_MOVE action when the mouse button
is not pressed.
Added some more plumbing for the scroll wheel axes. The values are
reported to Views but they are not yet handled by the framework.
Change-Id: I1706be850d25cf34e5adf880bbed5cc3265cf4b1
/frameworks/base/core/java/android/view/ViewGroup.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/ViewGroup.java
|
| add6577a0196258e5a48c5deefcdb12e05c935b3 |
|
10-Feb-2011 |
Chet Haase <chet@google.com> |
Fix animation and layoutTransition issues.
There were some subtle timing issues in animators with ending animations that
were not completely initialized (possibly because a startDelay'd animator
was ended before the delay elapsed).
Also, LayoutTransition had bugs around running a transition on a container
while a previously-started transition was still in progress. This could result
in some minor artifacts or crash bugs, depending on the durations and delays set
on the transition animations.
Change-Id: Ic6a69601f1ce9a55db15fff6b8ed25950b354491
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 85cabc2eb367e8dcbe7445886bdd945e47d1bbfa |
|
07-Feb-2011 |
Mike Cleron <mcleron@google.com> |
am 9cfa9c7a: am f6141980: Merge changes I46acd27a,I70b322e1 into honeycomb
* commit '9cfa9c7a3f5f23dec6ef4575407c1076d1b3c479':
aa is better than cc
Prevent ProgressBar from slowing down everything. bug #3422568
|
| 8b113cf6d78bdb673e97400951b0829d722dba2b |
|
04-Feb-2011 |
Romain Guy <romainguy@google.com> |
am cb2c84fd: am 3b66e43e: Merge "Refresh display lists when turning off layers rendering. Bug #3420565" into honeycomb
* commit 'cb2c84fd81a0891071e8ed0237927ad785751850':
Refresh display lists when turning off layers rendering. Bug #3420565
|
| 2f57ba56b3d4648476f0c00bd74fc4f6aa052810 |
|
04-Feb-2011 |
Romain Guy <romainguy@google.com> |
Prevent ProgressBar from slowing down everything.
bug #3422568
Change-Id: I70b322e140a8fdbe504c6984c54a22bcb7b753e7
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 9d18f2d189aa2670d96462f2220ee7fd7950ebe5 |
|
03-Feb-2011 |
Romain Guy <romainguy@google.com> |
Refresh display lists when turning off layers rendering.
Bug #3420565
Change-Id: I2139540e591a97cd487e3d7cce6b70d6b23df9de
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 44fbc03f651ce79b0726a6bb585567918a88e29c |
|
02-Feb-2011 |
Romain Guy <romainguy@google.com> |
am 57188f0d: am c1f8bcff: Merge "Fix incorrect dirty rectangle transformation in hardware layers. Bug #3413433" into honeycomb
* commit '57188f0d1d7225991f8f5afb2740ed4cc878305b':
Fix incorrect dirty rectangle transformation in hardware layers. Bug #3413433
|
| beff8d83ef062975459f149ad0c632a3797d78ce |
|
02-Feb-2011 |
Romain Guy <romainguy@google.com> |
Fix incorrect dirty rectangle transformation in hardware layers.
Bug #3413433
Change-Id: Iba201c7c4b4f11937797f3afcbf20c5a7395be25
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 34cdf5bbb7d4d09e95cc6579a96c384284f99455 |
|
02-Feb-2011 |
Romain Guy <romainguy@google.com> |
am debeeef5: am d51eaa64: Merge "Update layers based on the dirty region. Bug #3413433" into honeycomb
* commit 'debeeef50408cf12f1041426e7438be266789a62':
Update layers based on the dirty region. Bug #3413433
|
| 3a3133d876caf60ebff2176ad75c3dcf0259148d |
|
02-Feb-2011 |
Romain Guy <romainguy@google.com> |
Update layers based on the dirty region.
Bug #3413433
This helps Launcher when a widget updates during a scroll, or when interacting
with widgets on the workspace if layers are still turned on.
Change-Id: Ic7a42eb34f74f4ae988039754f815e2efd1d1e4f
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 4e96efe2edb73a8fbe4b89e85e03327da9796d80 |
|
02-Feb-2011 |
Romain Guy <romainguy@google.com> |
am a42ee699: am 518813ec: Merge "New API to let apps draw without layers. Bug #3413433" into honeycomb
* commit 'a42ee6994b59c02a745cb5d0f8ec257d01424753':
New API to let apps draw without layers. Bug #3413433
|
| 849d0a37cf2ca6c6a6c2d4d4456495e32e363120 |
|
02-Feb-2011 |
Romain Guy <romainguy@google.com> |
New API to let apps draw without layers.
Bug #3413433
Launcher now enables layers all the time, but in some cases (for instance, when the
workspace is not scrolling,) it is more efficient to draw without the layer.
Change-Id: I625fb5b48506acda9ae75356fdbbe812c85f2aab
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 509e6cd89551d4222fab3dab9df190cc5e25666b |
|
01-Feb-2011 |
Romain Guy <romainguy@google.com> |
am 1c531f4a: am f222956c: Merge "Correctly set the alpha of a hardware layer before drawing it. Bug #3410819" into honeycomb
* commit '1c531f4a44c9ea61e74dbe2ded1b8dca0f83f790':
Correctly set the alpha of a hardware layer before drawing it. Bug #3410819
|
| 54229ee5eb92e3e2fc63d75353bcf09e0ebc8030 |
|
01-Feb-2011 |
Romain Guy <romainguy@google.com> |
Correctly set the alpha of a hardware layer before drawing it.
Bug #3410819
Change-Id: I3ebaca2233f4edf5b59d84ec7706555056a1a4b1
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 38d1f2530829ae14d5ee9bf7871cb359dbf03f89 |
|
28-Jan-2011 |
Chet Haase <chet@google.com> |
am 19312cfe: am 246bf85a: Merge "Fix NPE with display lists when view not attached" into honeycomb
* commit '19312cfef15608fca2c8403dc240e8ec4f54d6b7':
Fix NPE with display lists when view not attached
|
| f4ac547f868db7c8a358e1f6e3d8fcebb02dbd49 |
|
27-Jan-2011 |
Chet Haase <chet@google.com> |
Fix NPE with display lists when view not attached
There was logic in ViewGroup that assumed that an accelerated
view must always be able to get a display list for any child
that it was drawing. One situation occurred, however, that
caused a problem with this - a contacts activity was started
and not yet attached, but was being asked to render into an
accelerated canvas. We assumed that the child would have a display
list and simply called getDisplayList(). But since that call
returned null, we later deref'd the null object.
The fix is to check whether a child can have a display list
instead of assuming that it can just because the container view
is accelerated.
Change-Id: I7de62fd597ad50720c9585d621bec02e77c171df
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 75b8c858ab43375092da06658b6046a007eb85ef |
|
27-Jan-2011 |
Chet Haase <chet@google.com> |
am cd88c39b: am e38ba4ac: Fix gmail crossfade artifacts.
* commit 'cd88c39b989fc927016aa8d1c3794b872519d575':
Fix gmail crossfade artifacts.
|
| e38ba4acbe6f1536997ffb98d662fc3eff07add8 |
|
27-Jan-2011 |
Chet Haase <chet@google.com> |
Fix gmail crossfade artifacts.
Display lists could not handle custom views that did their
own draw dispatching, as is the case with gmail. This fix makes that
possible and display lists handle this case robustly. Now the
crossfade works because the display lists contain the right content.
Change-Id: Iea7d6e99239b24f833701d546fe083aa00e2b31b
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 82782446cd0ea26604fcbd22d4b7e3608f32136d |
|
27-Jan-2011 |
Chet Haase <chet@google.com> |
am fcf51a67: am a45c056e: Merge "Fix display List bugs" into honeycomb
* commit 'fcf51a67967a402bf2178c3d0e09828e8942cade':
Fix display List bugs
|
| 678e0adbdbac5fa3f25ca8371fdff1b3182f67e9 |
|
25-Jan-2011 |
Chet Haase <chet@google.com> |
Fix display List bugs
Various property setters in View need to invalidate the parent's
cache to get redrawn properly when accelerated with display lists.
Also, fix logic around display lists and old-style Animations in
ViewGroup.
Change-Id: I70e1c2fa49e62228ee4a1301a006ce50bda4c305
/frameworks/base/core/java/android/view/ViewGroup.java
|
| e29131cac364d38e6ee598d190027a1b9bdda01d |
|
26-Jan-2011 |
Chet Haase <chet@google.com> |
am b69e985b: am ace9233b: Merge "Fix invalidation problem with display lists" into honeycomb
* commit 'b69e985b9aa059d6cf7498a2350d3f814b4cf711':
Fix invalidation problem with display lists
|
| 77785f9d257f663087a8c27957f506b9f7aa24c2 |
|
26-Jan-2011 |
Chet Haase <chet@google.com> |
Fix invalidation problem with display lists
It was previously the case that a view marked ~DRAWN must be
invalidated correctly already, so we would not mark any flags.
Display lists added new logic such that an undrawn node must still
be checked to see if its cache has been marked invalid. If not,
we must mark it invalid to make sure that a future rendering call
will cause the view to refresh its display list, thus refreshing its
child node tree's display lists, since that's where the invalidate
call must have originated.
Change-Id: I0f73c85459174c0e3f16d703f7eb914a706c808a
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 335f1513d7644a62e8d1a5b47befd950371d4665 |
|
25-Jan-2011 |
Romain Guy <romainguy@google.com> |
am b372d7cb: am 89fca351: Merge "Make nested hardware layers work again" into honeycomb
* commit 'b372d7cbea0b80cda3c7b08dcaddbd5c398911b2':
Make nested hardware layers work again
|
| 5e7f766e99c679110fa95501728bb81a8e396e58 |
|
25-Jan-2011 |
Romain Guy <romainguy@google.com> |
Make nested hardware layers work again
Change-Id: I97bde694ec1b712a1e010c8137919e6d64af3148
/frameworks/base/core/java/android/view/ViewGroup.java
|
| caf48e95e7ce9417c1f89aa28bc262b9ffd90797 |
|
25-Jan-2011 |
Romain Guy <romainguy@google.com> |
am 7b4950ae: am 169fafe6: Merge "Fix rendering issues with animated layers. Bug #3385247" into honeycomb
* commit '7b4950ae350255a393125cc4262925b432770ac4':
Fix rendering issues with animated layers. Bug #3385247
|
| 8168396d1acbcb5fdd29eeda4c30b2803d5283ae |
|
25-Jan-2011 |
Romain Guy <romainguy@google.com> |
Fix rendering issues with animated layers.
Bug #3385247
- The layer's alpha was interpreted in the wrong range 0..255 instead of 0..1
- 9-patches would not correctly dirty the layer region, the generated mesh
was incorrect
Change-Id: I4916249bedcdb0794929f3796bd17854971efc88
/frameworks/base/core/java/android/view/ViewGroup.java
|
| e965dee34135e7bce186408d1265a5cfd05a9fb1 |
|
25-Jan-2011 |
Romain Guy <romainguy@google.com> |
am 4e1db6da: am 2ff6d705: Merge "Enable partial invalidates when rendering with OpenGL." into honeycomb
* commit '4e1db6dadd404c023b71ae1ab54e990fce56abc3':
Enable partial invalidates when rendering with OpenGL.
|
| 2ff6d70521fe1f537f8ebd631f0b9b3aa8becf94 |
|
25-Jan-2011 |
Romain Guy <romainguy@google.com> |
Merge "Enable partial invalidates when rendering with OpenGL." into honeycomb
|
| 7d7b5490a0b0763e831b31bc11f17d8159b5914a |
|
25-Jan-2011 |
Romain Guy <romainguy@google.com> |
Enable partial invalidates when rendering with OpenGL.
Change-Id: Ie8be06c4776b815e8737753eb8003b4fd8936130
/frameworks/base/core/java/android/view/ViewGroup.java
|
| f8ac62237babea7ec08ba71d00539f33d6ad560d |
|
25-Jan-2011 |
Chet Haase <chet@google.com> |
am 235a20a3: am 21d405f5: Merge "Fix for display list problem with listview items." into honeycomb
* commit '235a20a3d1b57492ba0fbebb7f9dcce41ef011d0':
Fix for display list problem with listview items.
|
| 3b2b0fc257b4c69cdd5c1f2885359786af6787df |
|
25-Jan-2011 |
Chet Haase <chet@google.com> |
Fix for display list problem with listview items.
We were not correctly invalidating items that were being attached
to listviews.
Change-Id: I5d29a82c4276f09e401c6869ab1e86a3c8281366
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 3873da3c6ee0a63de0d91e6045b7546402f4ce3d |
|
24-Jan-2011 |
Chet Haase <chet@google.com> |
am 2acb67ec: am 67005b05: Merge "Use optimized display lists for all hwaccelerated rendering" into honeycomb
* commit '2acb67ec9fe34316231519373f59dfb76c03d57b':
Use optimized display lists for all hwaccelerated rendering
|
| 10f4126a367071a49f208f10ceb1ed0e1151d48c |
|
24-Jan-2011 |
Joe Onorato <joeo@google.com> |
resolved conflicts for merge of faf083ef to master
Change-Id: I316a1b4356f6dba6c3880ccb02dbb2fa00d21a85
|
| daf98e941e140e8739458126640183b9f296a2ab |
|
10-Jan-2011 |
Chet Haase <chet@google.com> |
Use optimized display lists for all hwaccelerated rendering
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
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 664644d9e012aa2a28ac96f305b1ce6499ec8806 |
|
24-Jan-2011 |
Joe Onorato <joeo@google.com> |
visibility ("lights out") API.
1. Views may setSystemUiVisibility() to recommend that
the system chrome (status bar or other UI) show or hide
itself. (This functionality was previously available only
via the FLAG_FULLSCREEN window flag for some SystemUI
implementations.)
2. Views may register a OnSystemUiVisibilityChangedListener
on a view, and find out when the system UI actually
appears or disappears, allowing apps to coordinate the
appearance of their own UI if desired.
Bug: 3241144
Change-Id: Ia1758d94099182d49a1e3688ea2738ae4995b829
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 22da4dd48ec8c143d90126a0760a06774c4923a9 |
|
19-Jan-2011 |
Christopher Tate <ctate@google.com> |
am 714066d8: am 5383d077: Merge "Fix a couple of drag & drop crashes" into honeycomb
* commit '714066d873b70098c09c2c094d374781b12d65a2':
Fix a couple of drag & drop crashes
|
| 1fc014fd0051a48083c6d469c2a4f22da1aa15e4 |
|
19-Jan-2011 |
Christopher Tate <ctate@google.com> |
Fix a couple of drag & drop crashes
1. ViewGroups being removed from the layout during a drag would wind up
crashing the app with an NPE at drag-ended time, due to blind dereference
of now-cleared object pointers.
2. Passing a 'null' ClipData to startDrag() would crash the system
process with an NPE. Should this even be valid? I'm inclined to say
yes, though it means that apps will need to guard against it.
Fixes bug 3369542
Change-Id: I168fc1284d6fd4403999946609725414cf254df0
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 0f6226b9f417182bbf791598000f0a153fbf191c |
|
18-Jan-2011 |
Jeff Brown <jeffbrown@google.com> |
Merge "Add joystick support to framework."
|
| d6cd572df8067c40b3e0e7e74e58cdb456b33e92 |
|
17-Jan-2011 |
Romain Guy <romainguy@google.com> |
Improve hardware layers rendering speed when setting a View's alpha.
Change-Id: Ib1275677f531c60d9919978c5538c663fdb823b5
/frameworks/base/core/java/android/view/ViewGroup.java
|
| cb1404e45639d20439d7700b06d57ca1a1aad1fa |
|
16-Jan-2011 |
Jeff Brown <jeffbrown@google.com> |
Add joystick support to framework.
Change-Id: I95374436708752e1a9cff3f85c5b9bc3e0987961
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 86cab1bd52197d6fa60786413fad9788d9236762 |
|
14-Jan-2011 |
Christopher Tate <ctate@google.com> |
Send DRAG_STARTED notices to views that become visible during drag
We now recognize that a view is now a candidate for receiving the drop
but hasn't yet been notified about it, and send the DRAG_STARTED lifecycle
event properly. This change also changes the DRAG_ENDED policy: now,
every view that had been sent a DRAG_STARTED receives the corresponding
DRAG_ENDED event, even though subsequent visibility changes may have
occured.
Change-Id: If4ae9ddbf414703e9f15eb2005471626bf19f316
/frameworks/base/core/java/android/view/ViewGroup.java
|
| c15c7a79a69733bd21d6548fd74c2874fdabe7e8 |
|
13-Jan-2011 |
Romain Guy <romainguy@google.com> |
Merge "Cleanup implementation of hardware layers." into honeycomb
|
| ada830f639591b99c3e40de22b07296c7932a33f |
|
13-Jan-2011 |
Romain Guy <romainguy@google.com> |
Cleanup implementation of hardware layers.
The new implementation relies on OpenGLRenderer's existing layer
code instead of duplicating it. The new code is much cleaner, with
simpler and better APIs and allows tracking of drawn regions inside
layers. Region tracking is not yet enabled but this will be done
in a future CL.
Change-Id: Ie826121a2227de8252c77b992a61218defea5143
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 9c0874408cfc6f6f4e4561973ca5ae52a5982db7 |
|
13-Jan-2011 |
Chet Haase <chet@google.com> |
Supress layout requests while a LayoutTransition is running.
LayoutTransition works by animating layout-related properties
(left, right, top, and bottom). This works great when that animation
is the only thing affecting the layout of the UI. But if there are other things
happening in the application that cause layout to run on that
container or in its parent hierarchy, this can cause the layout properties
on its children to get mis-set during the middle of the transition.
This results in artifacts like animating objects jumping to locations where
they would be were there no animation running.
The fix is to supress layout requests on that container (and its children)
until the transition is complete (then issue a layout request on the container
to make sure that the container has the correct layout data)
Change-Id: I15bf0423a11409f854076f86099233db7fe4edc0
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 6c319ca1275c8db892c39b48fc54864c949f9171 |
|
11-Jan-2011 |
Romain Guy <romainguy@google.com> |
Better backend for hardware layers.
With this new backend, a hardware layer is only recreated when
its associated view is udpated. This offers fast composition
in GL and fast update of the layer in GL as well.
Change-Id: I97c43a612f5955c6bf1c192c8ca4af10fdf1d076
/frameworks/base/core/java/android/view/ViewGroup.java
|
| e95003e4a15eea2d5f93950fc46f99ff2b9c973a |
|
09-Jan-2011 |
Romain Guy <romainguy@google.com> |
Tighten up AsyncTask's semantics and behavior.
Bug #3109366
Bug #3109382
The new behavior of AsyncTask is the following:
- Unchanged if you don't call cancel()
- If you call cancel():
- Either onCancelled() *OR* onPostExecute() is invoked
- onCancelled() is invoked only after doInBackground() finishes
Change-Id: If53faec5890d2fa7098aea76973186a0b1026b39
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 7e68efb0a098149e1e6f86663e978e9fd26e0ea1 |
|
07-Jan-2011 |
Romain Guy <romainguy@google.com> |
Non-opaque views with fading edges cannot be marked dirty opaque.
Bug #3325084
Change-Id: I80b7653daa2ae3cc6d81da1063911aa4cb69e8f4
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 171c592f0b7066acf279863c8a52ddabea49d3db |
|
06-Jan-2011 |
Romain Guy <romainguy@google.com> |
New layers API for Views.
This API can be used to back a view and its children with either a
software layer (bitmap) or hardware layer (FBO). Layers have
various usages, including color filtering and performance
improvements during animations.
Change-Id: Ifc3bea847918042730fc5a8c2d4206dd6c9420a3
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 03ab0c7231a5c534b86eca28d875c6026ae09564 |
|
07-Jan-2011 |
Joe Onorato <joeo@google.com> |
some touch event debugging
Change-Id: I05d69da4db8c03f9c5131cd271bd9ee1b4996ca9
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 995e77431982f9a320451dbe6132a62e69f73bab |
|
23-Dec-2010 |
Jeff Brown <jeffbrown@google.com> |
Enable touch splitting by default for Honeycomb apps.
Also fixed some bad comments I noticed along the way.
Change-Id: I4328c8aaa22f48a5c1fd274e889abb7823747330
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 4e6319b73c85082e18d1c532b86336ddd1f8cfaa |
|
13-Dec-2010 |
Jeff Brown <jeffbrown@google.com> |
Add initial support for TAB navigation.
Bug: 3286652
Change-Id: I813a0318b3b8d9c9bc791ea6a2427be11c08de00
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 669084dbe6f1a20517964745028eff158c2c27e3 |
|
08-Dec-2010 |
Mathias Agopian <mathias@google.com> |
resolved conflicts for merge of a0f011ff to master
Change-Id: I4c17021fc269ce66c98cc345353600eda332f980
|
| e33811512eb061338792dbb0dbd37a1b8e4e1079 |
|
03-Dec-2010 |
Mathias Agopian <mathias@google.com> |
[3253328, 3171580] Treat GONE and INVISIBLE views the same when calculating transparent regions
We only used to check for INVISIBLE, which prevented some Surfaceview
optimization to take place.
Change-Id: I244b54696d861a022ca1c334ff61ab7efb899587
/frameworks/base/core/java/android/view/ViewGroup.java
|
| f2f7d8f9dd75c6e32a46a28fd3f53435addf0746 |
|
03-Dec-2010 |
Chet Haase <chet@google.com> |
Fix invalidation issue for optimized/GL case.
The bug caused intermittent artifacts where some apps would not get
repainted until some overall screen invalidation occurred.
Change-Id: I82a3294429f15fe51cc8f4b47134e3b5540cb240
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 0d200833fdc53f9796698f97c18cefc4a1b82df2 |
|
05-Nov-2010 |
Chet Haase <chet@google.com> |
Fix GL rendering of translucent surfaces
GL renderer was not initializing scissor correctly for translucent
surfaces, resulting in invisible window backgrounds in some cases
like fading popup windows
Change-Id: I87a964986e1ba2c4f59708c8892c5fa71903e6fc
/frameworks/base/core/java/android/view/ViewGroup.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/view/ViewGroup.java
|
| 9d1ab883293b047b654935b84d0803c8c383be91 |
|
02-Nov-2010 |
Chris Tate <ctate@google.com> |
Fix drag enter/exit reporting
Now, each ViewGroup is tracking which of its child views [which might
themselves be ViewGroups] is currently under the drag point, and when the
drag leaves that child, a DRAG_EXITED is synthesized and dispatched all
the way down to the leaf view previously under the point. ENTERED is
still *not* dispatched down like this; instead, it's calculated and
synthesized directly at each level based on the new LOCATION.
The ViewRoot still tracks the leaf drag target, but solely for the
purpose of reporting changes to the OS after full dispatch of a new
LOCATION -- the entered/exited messaging is no longer initiated at the
ViewRoot level.
Change-Id: I0089cc538b7e33a0440187543fcfd2f8b12e197d
/frameworks/base/core/java/android/view/ViewGroup.java
|
| a32edd4b4c894f4fb3d9fd7e9d5b80321df79e20 |
|
26-Oct-2010 |
Adam Cohen <adamcohen@google.com> |
Adding click feedback to widget collections
Change-Id: I97fceb6c68ca6eb1b703eafacf201e1aed7c38e7
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 70d4ba15b1f0c1133c5aabc86de828b41e482fff |
|
06-Oct-2010 |
Chet Haase <chet@google.com> |
Performance optimizations for animations and toolkit
Change-Id: I316a48273a9cbb428a965e4b849b3e5e9e8202f1
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 0d9275e565551eed57297627188aa39f3897a50b |
|
26-Oct-2010 |
Romain Guy <romainguy@google.com> |
Enable display lists.
Change-Id: Id0d9b987251da5b7ecbb5497a55dbb5937430316
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 5c13d89c1332fcc499379b9064b891187b75ca32 |
|
08-Oct-2010 |
Chet Haase <chet@google.com> |
Optimizing display lists by referencing pointers to resources instead of copying them
Change-Id: I81ad3551d74aa1e5bb64d69e33d2eb29a6c1eb6a
/frameworks/base/core/java/android/view/ViewGroup.java
|
| fb0547d2c0f84e8266dce1444d332433ada09249 |
|
20-Oct-2010 |
Patrick Dubroy <dubroy@google.com> |
Fix memory leak with TouchTargets not being recycled.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 32affef4f86961c57d9ba14572ec65dc2a5451de |
|
19-Oct-2010 |
Chris Tate <ctate@google.com> |
Introduce an OnDragListener mechanism
If the listener's onDrag(view, event) returns 'false', the view's own
onDragEvent() will be called. If the listener returns 'true', it
consumes the event (and declares that it will handle the rest of the
drag event sequence, in the case of DRAG_STARTED actions).
Change-Id: I01aff0e4f59f71e55f5eea1049905c80714f0607
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 67a2f7b5a1b3ec5d2440d8be6e5ee4274e90e226 |
|
14-Oct-2010 |
Romain Guy <romainguy@google.com> |
Never skip drawing SurfaceViews.
Change-Id: I07fbc632b01d96cee16b6e000e0cbf05238a442b
/frameworks/base/core/java/android/view/ViewGroup.java
|
| a3496a9e6011e73deadd33bd0edd9229512e23d3 |
|
12-Oct-2010 |
Romain Guy <romainguy@google.com> |
Fix invisible views issue in Launcher.
Change-Id: Ic7cb8f418b5879110eaea5a9c5fdb4f237ca4cab
/frameworks/base/core/java/android/view/ViewGroup.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/ViewGroup.java
|
| 5ada6cb0591c1106e3591a3b7adcdc77a1322209 |
|
05-Oct-2010 |
Christopher Tate <ctate@google.com> |
More drag/drop adjustments:
* Make View.onDragEvent() public instead of protected.
* No longer @hide View.startDrag()
* Properly manage the boundaries of DRAG_STARTED / DRAG_ENDED notifications
to windows (and as a result don't send bogus empty DRAG_STARTED events or
double-recycle pooled DragEvents)
Change-Id: Ib75f5c1417640c82a5b043c555e02d6e6f4b4d9c
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 469b1dbeaf7d3267d1b43af4e7391b49eac10ee0 |
|
05-Oct-2010 |
Romain Guy <romainguy@google.com> |
Code cleanup and disable display lists for now.
Change-Id: I681213036b5279339cb96a016d1dfb15d74dafc8
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 2c095f367779ef32130c72849936a2e3013c8492 |
|
04-Oct-2010 |
Christopher Tate <ctate@google.com> |
Refinements to drag/drop
Thumbnail measurement & drawing has been moved out into a delegate
class called View.DragThumbnailBuilder. This consolidates the
thumbnail-related code as well as ensuring that the drag initiator
does not have to know a priori where to place the thumbnail relative
to the touch point *before* the thumbnail measurement step, as was
previously the case.
startDrag() no longer needs to be told where the current touch point
is at the time the drag is launched.
Drag events are now dispatched only to VISIBLE views.
Dispatch shouldn't double-recycle events any more when the target
window is local to the system process.
Change-Id: I49419103765a0cad2e18ddfcdd6dacb94daf1ff1
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 5e25c2c14593caee5638603120553ae1ec530f85 |
|
16-Sep-2010 |
Chet Haase <chet@google.com> |
Add ability to automate animated transitions on View show/hide
Change-Id: Id6ff92c8fd06c3f5fb30c41b020b4de4f567154f
/frameworks/base/core/java/android/view/ViewGroup.java
|
| a53146c5569f8ff5f7eb55e9ad35d23ddacf2add |
|
07-Sep-2010 |
Christopher Tate <ctate@google.com> |
Drag/drop APIs and infrastructure
A View initiates a drag-and-drop operation (hereafter just called a "drag")
by calling its startDrag(ClipData) method. Within the processing of that
call, two callbacks are made into the originating View. The first is to
onMeasureDragThumbnail(). Similarly to the core onMeasure() method, this
callback must respond by calling setDragThumbnailDimension(width, height) to
declare the size of the drag thumbnail image that should be used. Following
this, the View's onDrawDragThumbnail(canvas) method will be invoked to
actually produce the bits of the thumbnail image.
If all goes well, startDrag() will return 'true', and the drag is off and
running. (The other arguments to startDrag() provide reconciliation between
the current finger position and where the thumbnail should be placed on
the screen relative to it.)
Potential receipients of the ClipData behind the drag are notified by a
new dispatch mechanism, roughly parallel to motion event dispatch. The core
routine is the View's onDragEvent(event) callback, with the mechanics of
dispatch itself being routed through dispatchDragEvent(event) -- as in
the case of motion events, the dispatch logic is in ViewGroup, with leaf
View objects not needing to consider the dispatch flow.
Several different event 'actions' are delivered through this dispatch
mechanism:
ACTION_DRAG_STARTED: this event is propagated to every View in every window
(including windows created during the course of a drag). It serves as a
global notification that a drag has started with a payload whose matching
ClipDescription is supplied with the event. A View that is prepared to
consume the data described in this event should return 'true' from their
onDragEvent() method, and ideally will also make some visible on-screen
indication that they are a potential target of the drop.
ACTION_DRAG_ENTERED: this event is sent once when the drag point
enters the View's bounds. It is an opportunity for the View to set up
feedback that they are the one who will see the drop if the finger goes
up now.
ACTION_DRAG_LOCATION: when the drag point is over a given View, that
View will receive a stream of DRAG_LOCATION events, providing an
opportunity for the View to show visual feedback tied to the drag point.
ACTION_DRAG_EXITED: like DRAG_ENTERED, but called when the drag point
leaves the View's bounds. The View should undo any visuals meant to
emphasize their being the hovered-over target.
ACTION_DROP: when the drag ends at a given point, the View under that
point is sent this event, with the full ClipData of the payload.
ACTION_DRAG_ENDED: paralleling the DRAG_STARTED action, this is the global
broadcast that the drag has ended and all Views should return to their
normal visual state. This happens after the DROP event.
Change-Id: Ia8d0fb1516bce8c735d87ffd101af0976d7e84b6
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 20e987bfc35d0ae6cb6344ead65ed44ee7cf8750 |
|
23-Aug-2010 |
Jeff Brown <jeffbrown@google.com> |
Add MotionEvent Matrix transformations.
Fixed issued in ViewGroup's transformation of MotionEvents to ensure
that the entire historical trace is transformed, not just the current
pointer.
Simplified the code in ViewGroup for splitting events across Views.
The new code also handles the case where some pointers are dispatched
to the ViewGroup in addition to its children whereas the previous
code would drop some pointers on the floor.
Change-Id: I56ac31903e1de8a9c376d9c935b7217b0c42d93e
/frameworks/base/core/java/android/view/ViewGroup.java
|
| b051e895ccb696604349c6c5efe7c4747e1d1ab6 |
|
29-Sep-2010 |
Romain Guy <romainguy@google.com> |
Add display lists caching.
Change-Id: Iac3a248a81ed8cb076a83ef9d186b8ebba685b4c
/frameworks/base/core/java/android/view/ViewGroup.java
|
| fd880425e058a039ed6483d822738b80f962eb08 |
|
24-Sep-2010 |
Romain Guy <romainguy@google.com> |
Don't clip alpha layers if the flag is not set.
Change-Id: I820fa66bc3699357677f37a769de52fd176d9416
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 879fb6b5d66bec90d3420fad12a2a9b2fe9592f3 |
|
20-Sep-2010 |
Adam Powell <adamp@google.com> |
Text selection anchors changed to use windows
Manually cherry-picked
Change-Id: Id080dfad0e2f324fef3a5175abc78f76c8bad4c8
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 9aed300279db6953356aed5ef24a42291f5829cb |
|
20-Sep-2010 |
Adam Powell <adamp@google.com> |
Text selection anchors changed to use windows
Change-Id: I14f138039f5e3175a8c07f21985715b8447708e5
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 5d8f9dd3572c9d3b3d57985c31427dc9ca2a7f4a |
|
18-Sep-2010 |
Adam Powell <adamp@google.com> |
am 99f0f367: am 4258bfb7: Merge "Fix some drawing artifacts/bugs around overlays/text anchors" into gingerbread
Merge commit '99f0f3676f50640dbb22bd12960f771fc414862e'
* commit '99f0f3676f50640dbb22bd12960f771fc414862e':
Fix some drawing artifacts/bugs around overlays/text anchors
|
| 23bd5f50759c54224a2620cbed4614e434437265 |
|
18-Sep-2010 |
Adam Powell <adamp@google.com> |
Fix some drawing artifacts/bugs around overlays/text anchors
Change-Id: I28170d4e120506c09a1cfea721244fbcd3c2576a
/frameworks/base/core/java/android/view/ViewGroup.java
|
| f37df070ea84c353ff8bed4b2591932126d7e2ca |
|
18-Sep-2010 |
Adam Powell <adamp@google.com> |
resolved conflicts for merge of b39470b5 to master
Change-Id: If441c8684c576b6cbc485a37088d6869ad3fb23f
|
| b08013c312e3d849029a2f4c11889274c00f438d |
|
17-Sep-2010 |
Adam Powell <adamp@google.com> |
Added overlay support for drawing/responding to text anchors.
Overlays let views draw and respond to touch events outside of their
bounds. This allows selection anchors to be friendlier and easier to
grab. This is currently private API, pending further evaluation.
Added themes/styles for text selection anchors.
Added assets for text selection anchors as provided by UX. The
left/right anchors are currently not suitable for use. They are here
for bookkeeping and replacement later. The theme currently uses the
'middle' anchor asset for all three. This will be changed once assets
are ready.
Change-Id: I01b21e5ae90cab201f86f38f2f5eeaf2bd7f6bcd
/frameworks/base/core/java/android/view/ViewGroup.java
|
| d0fa371f276fde32d81c037006941bc93da0bb03 |
|
15-Sep-2010 |
Dianne Hackborn <hackbod@google.com> |
Add a new "activated" state to View.
Use this in ListView and GridView if the top view is not checkable.
This allows PreferenceActivity to now highlight the current heading
that is being shown.
Change-Id: I0d28aded9a61a42962b4aece420ae4058712d963
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 167bc821ddfee3d6d3b1c0ea10636be7c6eb591a |
|
14-Sep-2010 |
Adam Powell <adamp@google.com> |
Fix bug 2995805 - splitMotionEvents behavior change
Changed the new split motion events behavior to match the enshrined
behavior. A return value of false from a target's dispatchTouchEvent
will not prevent the target from receiving further events in the
gesture unless it is the initial ACTION_DOWN event.
Change-Id: Ied8d531dfec7009a4124ed670b1700753c3f9caa
/frameworks/base/core/java/android/view/ViewGroup.java
|
| b20db3ec34e846010f389880b2cfab4d7bf79820 |
|
10-Sep-2010 |
Chet Haase <chet@google.com> |
Make fragment animations work when fragments go away
Change-Id: I136de6ef910cc02b8181fcfa065bdb0770841396
/frameworks/base/core/java/android/view/ViewGroup.java
|
| b380c4d7edc158788a85c906900232675c0164ac |
|
08-Sep-2010 |
Jeff Brown <jeffbrown@google.com> |
resolved conflicts for merge of a05088c1 to master
Change-Id: I7973f9f28586dec9b9659f8f662f40db7997a521
|
| 85a3176704b5bfbeece9bd928369fbb76eec7dc6 |
|
02-Sep-2010 |
Jeff Brown <jeffbrown@google.com> |
Add support for secure views.
Added the MotionEvent.FLAG_WINDOW_IS_OBSCURED flag which is set by the
input manager whenever another visible window is partly or wholly obscured
the target of a touch event so that applications can filter touches
accordingly.
Added a "filterTouchesWhenObscured" attribute to View which can be used to
enable filtering of touches when the view's window is obscured.
Change-Id: I936d9c85013fd2d77fb296a600528d30a29027d2
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 5429e1d1026db8922478b715672e6c0703bbf4a9 |
|
07-Sep-2010 |
Romain Guy <romainguy@google.com> |
Use static final debug fields.
Change-Id: I304c39f54f609729bcec581091f285b2baa6fefa
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 13cc1207fab68adc5c7da0bf3b365196e26a273e |
|
04-Sep-2010 |
Chet Haase <chet@google.com> |
Add ability to enable layout transition animations by default from XML
Change-Id: I2b884c83e868f5d22ef85d65ff8ee984633de65e
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 21cd1389d2ef218b20994b617c57af120841a57f |
|
02-Sep-2010 |
Chet Haase <chet@google.com> |
Add transition effects for layout changes on ViewGroups
Change-Id: Ibefcca5692450188fbcec608f3f7e36be1213b21
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 9b34d45c8f164f1d4c51538f241263dfefc0f22e |
|
02-Sep-2010 |
Romain Guy <romainguy@google.com> |
Correctly apply alpha on TextView.
Bug #2969691
Change-Id: Ied46e9a38718cb37df10f9dc79b48fbc3a8bd237
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 9b073948cfb84c0dd04f8a94ee1f7f263f027c83 |
|
20-Aug-2010 |
Adam Cohen <adamcohen@google.com> |
Cleanup and bug fixes in StackView
-> pushed functionality from AdapterViewAnimator to StackView
-> only modifying clipping flags as far up the view
hierarchy as needed
-> still need framework level solution for drawing outside bounds
ViewGroup touch dispatch temp fix
-> Touch event was being modified and not reset in some
code paths.
Change-Id: I8135b62e2d73f239b9df407b0fa93bc434796989
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 816c3be1d7e27ee91ad4e87d39a208dbdc27c8f9 |
|
24-Aug-2010 |
Adam Powell <adamp@google.com> |
Fix some issues with touch event splitting around event timing
Change-Id: I15d04d226c218ad7b8a5fe43a55c33c3ade2128d
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 2b342f0a76f3237e97f15dc2f4e8a0b72dd7c023 |
|
19-Aug-2010 |
Adam Powell <adamp@google.com> |
Allow ViewGroup to split MotionEvents to multiple targets during dispatch.
Use the layout xml attribute splitMotionEvents="true" or the ViewGroup
method setMotionEventSplittingEnabled(true) to enable motion event
splitting. Rules for splitting are as follows:
* Splitting is enabled per ViewGroup. When splitting is enabled any
MotionEvent dispatched to that ViewGroup can potentially be split
into several and dispatched to children independently.
* Each pointer is assigned a target child view when the ACTION_DOWN or
ACTION_POINTER_DOWN event is received. That will be the pointer's
target until it goes up, the target returns false from onTouchEvent,
or the MotionEvents are intercepted.
* Multiple pointers may be assigned to the same target. All pointer
data sent to a target are bundled into a single MotionEvent. Child
views do not need to be aware that splitting has occurred.
Change-Id: I993f838e2f6b455da9812f4742a016dfcd1c4cc9
/frameworks/base/core/java/android/view/ViewGroup.java
|
| ecb1d5ded9afee63735dc91cfb08ada2c639d237 |
|
11-Aug-2010 |
Konstantin Lopyrev <klopyrev@google.com> |
resolved conflicts for merge of f00ee0f7 to master
Change-Id: I13b968bde37fad8fffdaa9bb94a0f1da9b2e6e0c
|
| bea95162ca25bd00b0479d93739b6283795c3986 |
|
11-Aug-2010 |
Konstantin Lopyrev <klopyrev@google.com> |
Categorizing exported view properties.
Change-Id: I79c42019836973d80662c21d195d088ae01537a0
/frameworks/base/core/java/android/view/ViewGroup.java
|
| fd2b002bcfca73958233a4e83a737612393e8a16 |
|
06-Aug-2010 |
Chet Haase <chet@google.com> |
Add 3D rotation to View
Change-Id: I4aa2542eb821e82d44e13d69b0938de13ffd4f0d
/frameworks/base/core/java/android/view/ViewGroup.java
|
| df030d2c160ff42927c58ff54c51049c69a48312 |
|
31-Jul-2010 |
Chet Haase <chet@google.com> |
View x/y properties now feed into matrix translation
Change-Id: I35d8953ab6c7a511cdf90f3f94a4a1b5ef549fc3
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 6e34636749217654f43221885afb7a29bb5ca96a |
|
23-Jul-2010 |
Adam Powell <adamp@google.com> |
Moved context modes into view, renamed to action modes
ContextualMode renamed to ActionMode. Adds a reference to the action
bar and reduces confusion around things named "Context".
Change-Id: Ia5098b1d0799a0ece0810c34e6696eda039fb005
/frameworks/base/core/java/android/view/ViewGroup.java
|
| ddc8e713ba345b24240fd16971283449c060a783 |
|
21-Jul-2010 |
Chet Haase <chet@google.com> |
Fix issue with touch MOVE events on transformed containers
Change-Id: I17e58f2c6acce606a672756d48d20eb0796b69e8
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 33e72aef05c75699c9180626dbaa00b06f86ad5b |
|
17-Jul-2010 |
Romain Guy <romainguy@android.com> |
Make View transforms work again.
Change-Id: I42aa8b5a55d7584ed242e1cb1f7123a6354edbc8
/frameworks/base/core/java/android/view/ViewGroup.java
|
| b5de9f3bafae2c30e7a67faa1cdf7d1c161820c3 |
|
17-Jul-2010 |
Adam Powell <adamp@google.com> |
Fix bug 2845609 - Touch event dispatching problem.
Maintain the state of the CANCEL_NEXT_UP_EVENT flag properly.
Change-Id: I5ca22409bf8557c486d02806811b10550c5576eb
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 9bc829cc15757edd149a61868426b214430a1c24 |
|
16-Jul-2010 |
Chet Haase <chet@google.com> |
Fixing view property invalidation issues
Change-Id: I51d2c03cabacfc1a7c05073977e7c22d32de7cb3
/frameworks/base/core/java/android/view/ViewGroup.java
|
| c3aa361d65119de503224202ae2296dbb1d3cf33 |
|
17-Jun-2010 |
Chet Haase <chet@google.com> |
Add various properties to View to allow it to be moved, scaled, faded, and rotated by property manipulation instead of just Animation operations.
Change-Id: Iefab11f243c7511f7bba0e32bd399ed716b9131f
/frameworks/base/core/java/android/view/ViewGroup.java
|
| c047b956360a2476793b38d9d3e996fed941af8b |
|
23-Jun-2010 |
Adam Powell <adamp@google.com> |
am bc337d2f: am 73ccafb5: Merge "Fix a bug where requestDisallowInterceptTouchEvent does not get called when scrolling is resumed after stopping a fling." into gingerbread
Merge commit 'bc337d2f675e8417be5534439e1b4ed1bc45a9c7'
* commit 'bc337d2f675e8417be5534439e1b4ed1bc45a9c7':
Fix a bug where requestDisallowInterceptTouchEvent does not get called
|
| 110486f932510fb49bfeff978b0b0e0237ee0656 |
|
23-Jun-2010 |
Adam Powell <adamp@google.com> |
Fix a bug where requestDisallowInterceptTouchEvent does not get called
when scrolling is resumed after stopping a fling.
Change-Id: I6796c5082cb81b3116de5baf1f27fe3addb40d00
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 4846032ac7be7c28c7cfeb3096b8cb656312a382 |
|
11-Jun-2010 |
Chet Haase <chet@google.com> |
Fix bug with layout animations when apps are auto-scaled.
The pivot points in RotateAnimation and ScaleAnimation are in pixel coordinates. When an app is being autoscaled, these values are incorrect and should be adjusted for the current scale factor. The fix adds API to Animation to allow ViewGroup to pass in the scaling factor.
Change-Id: I978c48f9b5aea6760148435e74e1a8d49e2f785d
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 2d6145993e19d2bb664766dbaf3c1e9ad3d12cdc |
|
10-Jun-2010 |
Romain Guy <romainguy@google.com> |
Move OpenGL support out of ViewRoot into a new HardwareRenderer class.
Change-Id: Iffaed924a5defc3c4df26223c390dc27eee115b1
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 812ccbeb3ce55c50463fda1d161b2eeed8b19cd2 |
|
01-Jun-2010 |
Romain Guy <romainguy@google.com> |
Add new hardwareAccelerated manifest attribute to enable HW drawing.
Change-Id: I2bb0252f3699cb720e7f5b6868419c9904e4fb35
/frameworks/base/core/java/android/view/ViewGroup.java
|
| b4bc78b16a05554c57508b488e21dd8eca4e13e6 |
|
13-May-2010 |
Dianne Hackborn <hackbod@google.com> |
Further work on fragments:
- Implement all of the state saving and restoring machinery. This
caused some flux in the API.
- Add ability to have fragments that are retained across activity
instances.
- Fix some bugs.
Change-Id: Ib6b5b0752d7f8d667cfdcd3e76d127cc9b6d901b
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 203688c6579bc530288642972d1f872a12516dfe |
|
13-May-2010 |
Romain Guy <romainguy@google.com> |
Fix dump of the persistent drawing cache attribute.
Change-Id: I351028f6e0858c9ebf7f59bd6cc964925bc3e2b9
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 3d5f648f8fe61507107b900fc3c4cf79b19572c6 |
|
26-Mar-2010 |
Dirk Dougherty <ddougherty@google.com> |
doc change: cherry pick 75c66da20927e7e854397c00ef1974140270c57f. (clarify fill_parent/match_parent transition in ViewGroup.LayoutParams and R.attr. Mention match_parent in dev guide "declaring layout" doc.)
Change-Id: I1d2b80b8dc3f8b2e3c1befcbb7c4c522d78a2db8
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 75c66da20927e7e854397c00ef1974140270c57f |
|
26-Mar-2010 |
Dirk Dougherty <ddougherty@google.com> |
sdk doc change: clarify fill_parent/match_parent transition in ViewGroup.LayoutParams and R.attr. Mention match_parent in dev guide "declaring layout" doc.
Change-Id: I07f6858f78e3b48ccaa99e87d81d18bf0499bdc0
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 65554f27855ce1764123604b061b10346f8b8404 |
|
23-Mar-2010 |
Romain Guy <romainguy@android.com> |
Improve export to bitmap layers for HierarchyViewer.
- Do not show layers with an invisible parent
- Correctly draw extras from dispatchDraw() (ListView's dividers for instance)
Change-Id: Id2e24ae9d52879290dffbf1cc446c5eda9522fbb
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 223ff5c0586adbbd1d6d57a3a4d176222e8b7434 |
|
03-Mar-2010 |
Romain Guy <romainguy@android.com> |
Add new CAPTURE_LAYERS command to HiearchyViewer protocol.
This command is used by the desktop tool to export a given view hierarchy into
a layered file format.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 8afa515936e78ccfc5563ca9164dc9a50ca73db4 |
|
26-Feb-2010 |
Romain Guy <romainguy@android.com> |
Send cancel event to recycled views instead of an up.
Bug #2309387
This was a problem in lists with list items that would cause notifyDatasetChanged()
interleaved with a series of up/down motion events. This is a pretty rare case
but it's worth fixing it to avoid getting views in a weird state.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| dcc490f20103a4bbd879ea040ce67779d211c2d7 |
|
25-Feb-2010 |
Romain Guy <romainguy@android.com> |
Fix the build.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| a440b002aa59e1455bdfa2c5a1ca51c74bbc19ac |
|
25-Feb-2010 |
Romain Guy <romainguy@android.com> |
Prevents ListView items children to modify properties of other children.
Bug #2464502
This fix introduce a new dispatch mechanism to tell views when they are temporary
detached/reattached from/to a ListView. This is very important to remove pending
callbacks or cleanup temporary states.
This change also modifies TextView which was relying on that callback in a very
particular case: a focused EditText in a ListView. The modified code acts only
when in that case, not if onStart/FinishTemporaryDetach() is called via
dispatch*() (== recycled views in ListView.)
/frameworks/base/core/java/android/view/ViewGroup.java
|
| e36d6e277e49475076b7872d36ea6a5c5b996e9d |
|
18-Feb-2010 |
Dianne Hackborn <hackbod@google.com> |
Work on issue #2263557: PMF3000 showing hybrid of portrait and landscape modes
This is a bunch of reworking of how configuration changes are handled:
- When orientation is changing (for whatever reason), the window manager no
longer tries to pre-emptively compute a new configuration. Instead, it
just determines change is happening and tells the window manager.
- The activity manager is now responsible for giving the window manager the
final configuration it is using. This is both so it knows whem the
activity manager is done with its configuration updates, and so the window
manager can use the "real" configuration.
- When an orientation or other configuration change is happening, freeze the
screen and keep it frozen until the activity manager has given us the
final configuration.
- The window manager can now send new configurations to its clients during
its layout pass, as part of a resize, if it has determined that it has
changed. This allows for a new View.onConfigurationChanged() API for any
view to easily find out when the configuration has changed.
- ViewRoot now also works with the activity thread to make sure the process's
current resources are updated to the new configuration when it receives one
from a window. This ensures that at the time onConfigurationChanged() and
other view callbacks are happening, the correct configuration is in force.
- There is now a sequence number associated with Configuration, which
ActivityThread uses to avoid using stale configurations. This is needed now
that it can receive configurations asynchronously from both the window
manager and activity manager.
- The hack for keeping the locale has been removed, and underlying problem
fixed by having Configuration initialize its locale to "unknown" instead of
a valid default value.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| f5c6eff63d19a9f7a970a4f90619edac873c006d |
|
10-Feb-2010 |
Gilles Debunne <debunne@google.com> |
Force layout on TableRows when column widths are shrinked or streched.
Also features some comment typos and import re-ordering.
Change-Id: I32cb14419d7d349064032718469daf62a0a72e3a
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 43c9cdffb619f93d9d4525dffd05701dc9c8c4bf |
|
27-Jan-2010 |
Romain Guy <romainguy@android.com> |
New View.dispatchDisplayHint() API.
Bug #2399147
This new API will be used by scrollable containers to tell children that they
are/are not displayed. This will allow lists to hide their filter popup window
for instance.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| bc9fdc92603112b3462024c8d0096b4eca3001c3 |
|
19-Jan-2010 |
Romain Guy <romainguy@android.com> |
Make sure the drawing cache is invalidated when reattaching a view.
Bug #2373677
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 980a938c1c9a6a5791a8240e5a1e6638ab28dc77 |
|
09-Jan-2010 |
Romain Guy <romainguy@android.com> |
Deprecate fill_parent and introduce match_parent.
Bug: #2361749.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 326d808b858359464b2ffeb84f2e0a8e0c79b600 |
|
10-Dec-2009 |
Adam Powell <adamp@google.com> |
Added View#dispatchViewVisibilityChanged and View#onDispatchVisibilityChanged; updated api; tests
Reverted a change to InstrumentationTestCase that would have allowed @UiThreadTest on setUp() methods of tests.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 293451e4f005a26386db873f5192f86585cc79bc |
|
04-Nov-2009 |
Romain Guy <romainguy@android.com> |
Remove unused field and add new API to control the children drawing order.
Approved by: xav, hackbod, mcleron.
Change-Id: I3bbfb4f96e3c9adedbb68d78703059a2df1e2013
/frameworks/base/core/java/android/view/ViewGroup.java
|
| fbd8f69a84163ef1cf52b07966320caf448c2bc9 |
|
26-Jun-2009 |
Romain Guy <romainguy@android.com> |
Fixes #1946141. Introduce new caching API to control scaling.
This change fixes issues with existing applications that access the drawing cache
directly. The API now lets application choose whether they want to get a scaled
drawing cache or not. The framework relies on the scaled cache for quality
purposes.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| cafdea61a85c8f5d0646cc9413a09346c637f43f |
|
12-Jun-2009 |
Romain Guy <romainguy@android.com> |
Fixes #1914574. An NPE could be causes in lists by ViewGroup.dispatchDraw().
ViewGroup was trying to access the AttachInfo without checking whether the
info object is null. The object can be null at varioous times in the lifecycle
of a list.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 8506ab4ac062d0e1ccde136e5e2f4081560e0c11 |
|
12-Jun-2009 |
Romain Guy <romainguy@android.com> |
Fixes #1886237. Views drawing cache was not generated properly.
In compatibility mode, a View's drawing cache was created at the 160 density
scale instead of the right scale.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| ec25df9fbc685be384f8dd764fa224a4d923e9d8 |
|
25-May-2009 |
Romain Guy <romainguy@android.com> |
Fix drawing bug: opaque invalidations should not be taken into account when the invalidated view is animating. Also add the ability to disable the auto-fade on the GestureOverlayView.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| d6a463a9f23b3901bf729f2f27a6bb8f78b95248 |
|
22-May-2009 |
Romain Guy <romainguy@android.com> |
Add a new API to ListView: setGestures(int). This allows developers to enable gestures to jump inside the list or filter it. This change also introduces a new XML attribute to control this API. It also adds the ability to theme the GestureOverlayView from the gestures library. Finally, this adds a new VERSION header to the binary format used to store the letters for the recognizer.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 75986cf9bc57ef11ad70f36fb77fbbf5d63af6ec |
|
15-May-2009 |
svetoslavganov <svetoslavganov@google.com> |
Accessibility feature - framework changes (replacing 698, 699, 700, 701 and merging with the latest Donut)
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 5bcdff45bf4ada77ae7c95f520b795876adef75c |
|
15-May-2009 |
Romain Guy <romainguy@android.com> |
Fixes #1846038. The dirty region can sometimes be modified by SurfaceFlinger. When this happens, force the view hierarchy to ignore the dirty flags.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 13922e03037d71a538f24ddf61c0b61bb4eb5af0 |
|
13-May-2009 |
Romain Guy <romainguy@android.com> |
Fixes #1836075. Adds consistency checks for the View hierarchy. To enable them, you need a debug build and ViewDebug.sConsistencyCheckEnabled set to true in debug.prop. This change also lets you easily enable drawing and layout profiling in ViewRoot by setting ViewRoot.sProfileDrawing, ViewRoot.sProfileLayout and ViewRoot.sShowFps in debug.prop with a debug build.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 24443ea3992e372e47daa50266b0f2ec38cac388 |
|
11-May-2009 |
Romain Guy <romainguy@android.com> |
Fixes #1596240. Optimize invalidate/draw passes by marking opaque views and avoiding drawing them. Whenever a View requests an invalidate its parent check whether the view is opaque or not. When the view is not opaque, the framework behaves as it used to. However, when a view is opaque, the parent marks itself as being dirty because of an opaque view. Its parent then does the same, and so on. When the framework then starts drawing the views, it does not draw views marked as dirty opaque. If a view is dirty opaque and receives an invalidate request from a non-opaque view, it then clears the dirty opaque flag and behaves as before.
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 8f2d94fd77836dac14319735e40f46b18b04216d |
|
26-Mar-2009 |
Romain Guy <> |
Automated import from //branches/donutburger/...@142820,142820
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 986003d46add147714ce7e16c9fefa8c18042fc8 |
|
26-Mar-2009 |
Romain Guy <> |
Automated import from //branches/donutburger/...@142790,142790
/frameworks/base/core/java/android/view/ViewGroup.java
|
| bb93d5598daa3312318c29401815bddf1df8c4de |
|
25-Mar-2009 |
Romain Guy <> |
Automated import from //branches/donutburger/...@141885,141885
/frameworks/base/core/java/android/view/ViewGroup.java
|
| 4df2423a947bcd3f024cc3d3a1a315a8dc428598 |
|
05-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@136594
/frameworks/base/core/java/android/view/ViewGroup.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/ViewGroup.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/ViewGroup.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/ViewGroup.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/ViewGroup.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/ViewGroup.java
|
| 54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/view/ViewGroup.java
|