On Mon, Apr 30, 2012 at 7:10 AM, JTeagle <teagle.ja...@gmail.com> wrote: > Consider the following revised example: > > > Widget 1 - natural height > Custom View A - largest height possible > Widget 2 - natural height > Custom View B - largest height possible > > Widget 3 - natural height > Custom View C - largest height possible > Widget 4 - natural height
You will have to create your own custom ViewGroup for that, AFAIK. And even then, it assumes an inaccurate definition for "largest height possible". > I cannot assume the position (order) of any of the widgets or views, since > I'm trying to build a framework that allows me to add (from a higher layer > of code) controls of any type in any order, to suit multiple applications, > without that higher layer having to have knowledge of how that is achieved. If the "higher layer" requests 10,000 widgets, you will not have enough room on the screen. Perhaps a ScrollView, with everything being "natural height", is a better approach. > Do you perhaps know how to reliably measure actual height controls (at what > point in the code can I get this information - a notification handler?). Write your own ViewGroup. > If so, can I manually resize the views at a later stage to fit (I assume I > can, and then simply call requestLayout() )? Write your own ViewGroup. > Or am I looking at deriving my own layout manager? That's what I mean by "write your own ViewGroup". :-) -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training...At Your Office: http://commonsware.com/training -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
