| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
These demos assumed the size of a tablet device and looked pretty
awful on phones.
Change-Id: I246ef5a5f4619c1f2fe689eca321314375722014
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When a container's child count goes to zero, it may report a measurement size
of zero. This affects LayoutTransition's fading-out of target views
because they may get clipped out by a layout that got sized to 0 because it
thinks it has no children. The workaround is to tell the layout to size itself
either with some minimal size (in the case of the FixedGridLayout used by some
demos) or with match_parent in some cases to ensure that the layout always has
some nonzero size.
Change-Id: I908e64d4fb054928af277a021a328e94477c9c83
|
| |
|
|
|
|
| |
Also fixed some existing bugs in some of the animation apps
Change-Id: Iff39a8396f8c49e2db8601b04012a0bb784a78ed
|
| |
|
|
| |
Change-Id: I3023db9d1f9cb8bf98b788fce4ae2b58b182987d
|
| |
|
|
|
|
| |
Originally, setting LayoutTransition animators to null just restored the default animation behavior, It seems more sensible to have null actually disable the animation. I made that change to the framework and modified this demo to show how it's done. Along the way, I refactored the code a bit and fixed some minor bugs.
Change-Id: Icfb53ada234b635294c5faa68a15932f25859fb8
|
| |
|
|
| |
Change-Id: Idb7ecb66b7dc0126a230385dd09af6a9208d5345
|
| |
|
|
| |
Change-Id: I0b3b5f1563ab0ac301684880957ed55ebfc54da5
|
|
|
Change-Id: Ib5f31bb0b6d16fa18cf10a426a25c7a8138f620a
|