The 2-LinearLayout system the demo used to have had its quirks, but was
just plain awful once it ran on a smaller screen. The new GridLayout
makes for a much better experience.
Change-Id: Ie3fd65e125c82da8b0079f61bd91bf844dea9b03
There were various minor issues with this app that made it not work
correctly in some situations (the APPEARING animation was basically a no-op,
and disabling the custom animations disabled animations altogether).
Change-Id: I20aba9551043a63c21d26208ae7cd0395cde01cb
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
New xml capabilities for animators, so I added new functionality
to the existing xml loading demo app
Change-Id: Iba30dce28059031744ce23d1f79f41072a6a1e78
Also, set hardwareAccelerated=false for animation demos using ovals
(which are not yet supported through GL)
Change-Id: I710b6be51a14bf02650206bd6bae8841ecd3ac79
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
