On Mon, Jun 15, 2009 at 7:00 PM, Matt <[email protected]> wrote:
> I said in a previous post that I thought the onMeasure/onLayout is a > bad design if onLayout is an unnecessary step for subclasses to > implement. We've clarified that it isn't an unnecessary step, but > implemented differently in various layouts, so I certainly don't think > the design is bad. However, like I said above, I argue that if > ViewGroup is rightly vague on how to implement it, the actual > implementations shouldn't be vague in their documentation. And after > all this work in this thread, I would volunteer to write the extra two > paragraphs if I could! Hopefully anyone Googling will find this, with > all of our mention of RelativeLayout, LinearLayout, ViewGroup, > onMeasure, and onLayout. If you want to add documentation, it should primarily be to not subclass from a layout manager in order to modify how it does layout. That is just not supported. We definitely don't implementation details about how it currently implement these in the documentation. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
