| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
- update Callback2 interface
- update Gravity.getAbsoluteGravity() and Gravity.apply() to be more generic
by changing "boolean isRtl" parameter to "int layoutDirection"
- fix BiDiTests for RTL FrameLayout
Change-Id: I97bb456c22d5fd3ecb34f08564ce4dbed37e7459
|
| |
|
|
|
|
| |
- following spec proposal for having CSS3 like naming
Change-Id: Id5e316a2d9b54b9f20bbcb168fea6a3a83882e1b
|
| |
|
|
|
|
|
|
| |
- fix FrameLayout
- code refactoring on LinearLayout
- add more unit tests
Change-Id: I49302582c61aa31a4eb7eded92327b10408f71a4
|
| |
|
|
|
|
|
|
| |
- update layouts
- add Callback2 for RTL aware Drawable
- add unit tests
Change-Id: Ic64d0291e262170aff7297c6580b0b422eaa8d89
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
Change-Id: I8b016aff1f790fbeaf435170c1ff33455ec91204
|
| |
|
|
| |
Change-Id: I5166d7b2d283c577d5f95a15b1626b068cfa6bc6
|
| |
|
|
|
|
| |
Bug #3328711
Change-Id: Ic131f2feecbeec4a7250d47193c9794aa70d22ee
|
| |
|
|
|
|
| |
Bug #3327185
Change-Id: If9a897efd8766b158749d053dabee3477bf1b053
|
| |
|
|
|
|
|
|
|
|
|
| |
Bug #3259668
If a FrameLayout is measured with an UNSPECIFIED or AT_MOST spec,
it cannot correctly define the size of its children set to
match_parent. This change adds a second measurement pass similar
to what LinearLayout does in the same situation.
Change-Id: I20ac5203c2efc2e559f88b2c9573d4ad7df488b4
|
| |
|
|
| |
Change-Id: I94ebf4064e64daaa547263adbdce86bfb836d55d
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This extends the view hierarchy's measure pass to allow view to
propagate up to their parent additional information besides just
their measured size. They can now report that their measured width
and/or height should be larger than the size their parent is
limiting them to (even though by definition they need to contrain
their reported measurements to the limits imposed by the parent).
ViewRoot uses this information to determine if it should remeasure
the window with a larger size limit to try to make it fit.
Change-Id: I90af3b7a8ec45d0a5c003fb009857025209d83eb
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
Bug #2924495
Change-Id: Idc06a1a4177f116a4796cd2fc83388a1a9a9cdbf
|
| |
|
|
| |
Change-Id: I79c42019836973d80662c21d195d088ae01537a0
|
| |
|
|
| |
Change-Id: I022f458c73967eacc9487bf8d8119999395efda9
|
| |
|
|
| |
Bug: #2361749.
|
| |
|
|
| |
the events processing in the gestures overlay mechanism. Give better control of the various properties of the overlay through XML attributes.
|
| |
|
|
|
|
|
|
|
|
|
| |
#1748954 (New status bar fades into all white background): FrameLayout wasn't updating its foreground drawable when its padding changed, which would happen as the status bar is shown and hidden. To fix this I also ended up fixing a problem in the view debug stuff where we couldn't get a bitmap for a view that is the full screen size because it is too big... actually I just went ahead and added another function to snapshot the view hierarchy which works a lot better for us anyway.
#1737952 (Home screen icons overlap with the notification bar after exiting any camera app): Originally I punted this because it only happened in rare situations, but now that home is always portrait it happens a lot more so it is more important to fix. This involved a few things to clean up hiding/showing the status bar:
- We now determine when to hide and show it during layout, which allows us to do this at the time it is actually needed rather than during animation after we can actually catch it for the initial display of a window. This required tweaking the layout API so the policy can request a second layout pass if needed.
- When doing layout, we are now much more aggressive about skipping the layout of windows. Basically anything that we know will be hidden in the near future is ignored for layout, so that it doesn't glitch as it is transfered out of the screen. The theory being that it is better to leave it as it was originally placed while we are transitioning it out, than to switch it to something slightly more correct.
Original author: hackbod
Merged from: //branches/cupcake/...
Automated import of CL 143899
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
