That's actually how i look at Android Development - Figuring out workaround for the system limitations\bugs :)
On Monday, May 13, 2013 10:27:27 AM UTC+3, Y2i wrote: > > Piren, thanks for the advice. I do use the right scope to lookup > children and have no problems looking them up. It is the framework that > have problems :( > I also understand that the samples are just samples and half-baked. When > you try to complete the layout animation sample, it works if id is > @android:id/text1 and does not work if id is @+id/text1 > I'm also aware that the framework has many rough edges, like you cannot > use Loaders if you use setRetainInstanceState(true) on a fragment. Or > returning null cursor crashes Loaders, even though null cursors work fine > with AsyncQueryHandlers as they supposed to. So I'm not surprised that > LinearLayout sometimes works and sometimes does not. It is my job to find > workarounds. > > -- -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
