Part of the drawables for DpiTest is a nodpi directory, but the
LOCAL_AAPT_FLAGS didn't specify it.
Bug: 3165492
Change-Id: I989068d76f922db6048e6db7cc6822ab3234d36e
Bug:2460543
Bug:3094312
Bug:2692655
Bug:2710595
Use the NEXT flag when there is a following
textfield.
In TextView, treat the new variations like email and password
variations.
Requires a change in LatinIME so that these fields work propely:
https://android-git.corp.google.com/g/#change,77721
Change-Id: Id6517a016db7d50b77570ff77f2635027796da4a
The TYPE_TEXT_FLAG_MULTI_LINE was set directly, instead of calling
setSingleLine, which has some side effects, like correctly updating
the mSingleLine field.
Generalized the use of setSingleLine everywhere. This may change some
behavior, but is probably fixing more state inconsistencies.
Change-Id: I6b4da2e140a8dc75481cff9e44473daa6b3a83c4
* commit 'b20c2e7ca03f5ef2694b20ff9a7a10a7249eb936':
[3163098] Fix bug in angleChange funtion which caused the returned angle change to be zeroall the time. The fix is to use PrevR instead of computing the difference between R and R.
Moving some of the code (finding which kind of file it is and
deleting parts of the url) to Java from C++.
Is needed by the following change in external/webkit:
https://android-git.corp.google.com/g/#change,77383
Change-Id: Ifc6008501eb580a0aaa5e307732b6f49ebd19ac4
The previous version of PropertyValuesHolder handled construction fine,
but setting new values did not result in things getting completely set
up correctly for interpolation between those new values.
Change-Id: Ibffb16e58b4fe76b8d1cad6f0224ffd4d5404c05
Remove transition delay to show home.
Add new constants to allow finer tuning of "success" animation.
Transition all items to transparent on successful unlock.
Change-Id: Id9f57b9bfc08be840d9282f987925617d2b42ea1
Who knew there were so many Loopers in the system server?
This adds dropbox logging for the activity manager thread, policy
thread, and window manager thread.
The goal's to catch more stuttering.
Change-Id: I3ce8518ce183b3c90426750a2992e67200fee5d5
drawColor() was not calling quickReject because it fills the clip region
and thus always passes the test. However, quickReject also checks whether
the current layer is invisible. drawColor() now performs the same check
and avoid drawing inside an invisible layer.
Change-Id: I63d0e9a8a9c0fba774f0f5c3870d58e6ed96fbd1
Add the ability to restrict a FragmentTransaction's ability to be
added to the back stack. (It doesn't make sense for tabs or other
scenarios to allow this.)
Change-Id: I8fa2edb5f35c365e2483010ad13eb9993f5e6570
While the difference is pretty minor since it's a small class,
the point is that the unit test will ensure that we detect
new methods added to FloatMath more easily.
Change-Id: Ia8bfee231cc4ae0cfeb18692be86d02649c187d5
This is used to allow list view's pressed and activated indicators
to fade in an out, though of course it can be used elsewhere as well.
There is a lot of complexity in supporting this in list view. The
two main things that are being dealt with:
- When recycling views, we need to make sure that the view's drawable
state doesn't get animated from an old row's state. The recycler
now keeps track of which position a view was last in, and if it is
reused at a new position there is a new View/Drawable API to tell
it to jump to its current state instead of animating.
- For the pressed indicator to fade out, we need to keep displaying it
after it is hidden. There are new variables and code to keep track
of this state, and tweaks in various places to be able to remember
the last selected position and continue updating the drawable bounds
as needed.
Change-Id: Ic96aa1a3c05e519665abf3098892ff2cc4f0ef2f